fix: move minimum-release-age to pnpm-workspace.yaml, fix Socket package downgrades#136
Merged
John-David Dalton (jdalton) merged 2 commits intomainfrom Apr 4, 2026
Merged
Conversation
…age downgrades - Move pnpm's minimum-release-age from .npmrc to pnpm-workspace.yaml to avoid npm v11+ warning about unknown config key - Keep min-release-age=7 in .npmrc for npm - Fix update script: bypass age gate for @socketsecurity/* and @socketregistry/* via env override (prevents downgrades)
…ion test The two clock-skew tests didn't actually test clock skew — they just did set/get/clear without creating far-future entries. They were slow (filesystem IO) and caused CI worker timeouts. Replaced with a single memoized TTL expiration test that verifies entries expire after TTL.
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.
Summary
minimum-release-agefrom.npmrctopnpm-workspace.yaml(minimumReleaseAge) to avoid npm v11+Unknown project configwarningpnpm update @socketsecurity/* --latestwas downgrading packages younger than 7 days. Now bypasses age gate vianpm_config_minimum_release_age=0env for Socket packagesTest plan
pnpm run updateno longer downgrades Socket packagespnpm config listshowsminimumReleaseAge=10080from workspace