chore(repo): prune stale minimumReleaseAge exemptions - #1128
Conversation
|
Apollo Coded App preview deployments are ready.
|
There was a problem hiding this comment.
🟢 Approval recommended
The change is a low-risk config cleanup, with only a minor follow-up needed to adjust a couple of now-stale inline comments elsewhere in the same file.
Pull request overview
This PR keeps the repo’s pnpm 14-day quarantine configuration tidy by removing minimumReleaseAgeExclude entries that have aged past the quarantine window and no longer require exemptions.
Changes:
- Removed stale, version-scoped
minimumReleaseAgeExcludeentries frompnpm-workspace.yaml. - Leaves only the still-relevant exemptions (scoped globs and currently-vetted pinned versions).
File summaries
| File | Description |
|---|---|
| pnpm-workspace.yaml | Prunes aged-out minimumReleaseAgeExclude exemptions to keep quarantine bypasses minimal and current. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Dependency License Review
License distribution
Excluded packages
|
📊 Coverage + size by packagePer-package bundle size on this PR (no JS/TS source changes detected under
"Coverage" is each package's own |
Storybook visual diff✅ No stories are affected by this PR's changes; nothing to compare. Logs Updated (PT): Sep 07, 2026, 02:18:58 AM |
Summary
The following packages were in `minimumReleaseAgeExclude` in `pnpm-workspace.yaml` because their latest release was too new at the time. Their latest versions are now older than the 14-day quarantine and no longer need an exemption.
nanoid@3.3.18dompurify@3.4.13mermaid@11.16.1fast-uri@3.1.6@xmldom/xmldom@0.9.12hono@4.12.34framer-motion@13.1.0motion@13.1.0motion-dom@13.0.0motion-utils@13.0.0Automated by the Prune Release Age Exemptions workflow.