Pin rollup to 4.60.4 to satisfy deploy minimumReleaseAge policy - #63
Merged
Conversation
The deploy box's pnpm enforces a minimumReleaseAge supply-chain policy. The previous override (rollup@4: ^4.61.1) resolved to 4.61.1, published the same day, so `pnpm install --frozen-lockfile` failed with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION. Pin to 4.60.4 instead: still >= 4.59.0 (the advisory fix) but several weeks old, so it clears the policy. audit and build verified clean.
There was a problem hiding this comment.
Pull request overview
Pins the frontend’s rollup@4 override to an older, policy-compliant release to prevent pnpm minimumReleaseAge failures during deploys (while staying within the known-secure >=4.59.0 range referenced in the PR description).
Changes:
- Pin
rollup@4override to4.60.4(instead of^4.61.1) to satisfy the deploy box’sminimumReleaseAgepolicy. - Regenerate
pnpm-lock.yamlto reflect the pinned rollup version and its platform binaries (and corresponding@types/estreeresolution).
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| frontend/pnpm-workspace.yaml | Pins the workspace-level rollup@4 override to 4.60.4 with rationale comments. |
| frontend/pnpm-lock.yaml | Updates the lockfile to resolve rollup (and its platform binaries) at 4.60.4. |
| frontend/package.json | Pins pnpm.overrides["rollup@4"] to 4.60.4 to match the workspace override. |
Files not reviewed (1)
- frontend/pnpm-lock.yaml: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Cwooper
added a commit
that referenced
this pull request
Jun 13, 2026
#63) The deploy box's pnpm enforces a minimumReleaseAge supply-chain policy. The previous override (rollup@4: ^4.61.1) resolved to 4.61.1, published the same day, so `pnpm install --frozen-lockfile` failed with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION. Pin to 4.60.4 instead: still >= 4.59.0 (the advisory fix) but several weeks old, so it clears the policy. audit and build verified clean.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The deploy on the Hetzner box fails at
pnpm install --frozen-lockfile:The server's pnpm enforces a
minimumReleaseAgesupply-chain policy. The rollup override added in #62 (rollup@4: ^4.61.1) resolved to 4.61.1, published the same day, so the policy rejected it (rollup + 25 platform binaries = 26 entries).Fix
Pin the override to
rollup@4: 4.60.4(in bothpnpm-workspace.yamlandpackage.json):>= 4.59.0, so it keeps clearing the original rollup advisory (GHSA-mw96-cpmx-2vgc).rollup ^4.43.0, so nothing else is affected.Lockfile change is rollup-only (its platform binaries +
@types/estree1.0.9→1.0.8).Verified locally (same minimumReleaseAge policy)
pnpm install --frozen-lockfile→ exit 0, no policy violationpnpm auditclean,vite buildok, 118/118 tests pass