Remove minimumReleaseAgeExclude for graphql-codegen packages - #493
Merged
Conversation
@graphql-codegen/[email protected] and @graphql-codegen/[email protected] (published 2026-09-01) are now well past pnpm's built-in 1-day minimumReleaseAge default window, so the exclude entries added when they were pinned are no longer needed. Verified with the pinned pnpm version (11.7.0 via corepack): a fresh frozen-lockfile install passes pnpm's supply-chain policy check without the exclude and does not re-add it. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01DZKSusdmEZmakEQJJfRqQH
|
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.
What
Removes the
minimumReleaseAgeExcludeentries for@graphql-codegen/cliand@graphql-codegen/plugin-helpersfrompnpm-workspace.yaml.Why
These excludes were added when
package.jsonwas pinned to@graphql-codegen/[email protected]and@graphql-codegen/[email protected](published 2026-09-01), since both versions were too new for pnpm'sminimumReleaseAgesupply-chain check at the time.The repo pins pnpm
11.7.0viadevEngines.packageManager, which defaultsminimumReleaseAgeto 1440 minutes (1 day) when unset. Both pinned versions are now several days old — well past that window — so the excludes are no longer needed.Verification
Activated the pinned pnpm version (
corepack prepare [email protected] --activate) and ran a freshpnpm install --frozen-lockfilewith the excludes removed:✓ Lockfile passes supply-chain policies).pnpm-workspace.yaml(it auto-writes them back if a pinned version is still immature — it didn't here), confirming both packages now pass the age check on their own.🤖 Generated with Claude Code
https://claude.ai/code/session_01DZKSusdmEZmakEQJJfRqQH
Generated by Claude Code