chore(repo): prune stale minimumReleaseAge exemptions - #1079
chore(repo): prune stale minimumReleaseAge exemptions#1079apollo-ui-release-bot[bot] wants to merge 1 commit into
Conversation
|
Apollo Coded App preview deployments are ready.
|
There was a problem hiding this comment.
Pull request overview
Removes now-expired minimumReleaseAgeExclude entries from pnpm-workspace.yaml, reducing the number of dependencies that bypass the 14-day minimumReleaseAge quarantine once their previously-vetted versions have aged out.
Changes:
- Removed stale version-scoped exemptions for:
nanoid@3.3.18,dompurify@3.4.13,mermaid@11.16.1,fast-uri@3.1.5,hono@4.12.34,motion-dom@13.0.0,motion-utils@13.0.0. - Kept remaining quarantine exemptions unchanged (e.g.,
@uipath/*, platform-binary globs, and current Motion v13 entries).
💡 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): Aug 24, 2026, 02:27:26 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.5hono@4.12.34motion-dom@13.0.0motion-utils@13.0.0Automated by the Prune Release Age Exemptions workflow.