Avoid fresh package releases in CI installs#311
Merged
Conversation
GitHub Actions now runs pnpm 11, which enforces the default minimumReleaseAge supply-chain policy during dependency status checks. The lockfile had resolved three packages published within that window, so macOS signing jobs failed before the build could start. Constraint: pnpm 11 rejects lockfile entries published inside the minimumReleaseAge window Constraint: Keep the supply-chain policy enabled rather than disabling it for release builds Rejected: Set minimum-release-age=0 | would weaken CI supply-chain protection globally Rejected: Wait for the 24 hour window | leaves repeatable release builds dependent on wall-clock timing Confidence: high Scope-risk: narrow Directive: Avoid committing freshly published dependency resolutions immediately before release builds; prefer mature pinned versions or refresh after the policy window passes Tested: pnpm install --frozen-lockfile --lockfile-only Tested: pnpm exec eslint package.json Not-tested: Full GitHub Actions matrix build Co-authored-by: OmX <omx@oh-my-codex.dev>
feng626
approved these changes
May 29, 2026
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
2 participants
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.
GitHub Actions now runs pnpm 11, which enforces the default minimumReleaseAge supply-chain policy during dependency status checks. The lockfile had resolved three packages published within that window, so macOS signing jobs failed before the build could start.
Constraint: pnpm 11 rejects lockfile entries published inside the minimumReleaseAge window
Constraint: Keep the supply-chain policy enabled rather than disabling it for release builds
Rejected: Set minimum-release-age=0 | would weaken CI supply-chain protection globally
Rejected: Wait for the 24 hour window | leaves repeatable release builds dependent on wall-clock timing
Confidence: high
Scope-risk: narrow
Directive: Avoid committing freshly published dependency resolutions immediately before release builds; prefer mature pinned versions or refresh after the policy window passes
Tested: pnpm install --frozen-lockfile --lockfile-only
Tested: pnpm exec eslint package.json
Not-tested: Full GitHub Actions matrix build