Skip to content

chore: add min-release-age to npm/pnpm/yarn config - #1

Open
rjain-g2 wants to merge 1 commit into
masterfrom
chore/min-release-age
Open

chore: add min-release-age to npm/pnpm/yarn config#1
rjain-g2 wants to merge 1 commit into
masterfrom
chore/min-release-age

Conversation

@rjain-g2

@rjain-g2 rjain-g2 commented Aug 6, 2026

Copy link
Copy Markdown

Adds a minimum release age to npm/pnpm/yarn config so newly-published
packages are not installed until they have existed on the registry for 7
days. This reduces exposure to fresh supply-chain compromises (Shai-Hulud
incident, Slack thread: https://g2dotcom.slack.com/archives/C0BN1V4EM25/p1785964332669229).

  • .npmrc: min-release-age=7 (days)
  • pnpm-workspace.yaml: minimumReleaseAge: 10080 (minutes)
  • .yarnrc.yml: npmMinimalAgeGate: 10080 (Yarn Berry, minutes)

Per-repo layer on top of a device-level default rolling out via MDM. Draft:
please confirm this does not conflict with a custom registry or lockfile
policy, and verify the repo lockfile is clean of known-bad Shai-Hulud
versions, before merging. Bun repos are handled by a separate sweep.

@upwind-code-us

upwind-code-us Bot commented Aug 6, 2026

Copy link
Copy Markdown

Upwind Upwind Code Scan - ✅ Proceed with Deployment

0 newly introduced vulnerabilities · 0 resolved · 0 total in this PR vs main

View full analysis in Upwind Console

Scan completed in 18s

Scan history (1 scan)
Commit Scanned at New Resolved Net
84ab536 < 2026-08-06 10:51 UTC 0 0 0

Last scanned: 84ab536 · 2026-08-06 10:51 UTC

@upwind-code-us

upwind-code-us Bot commented Aug 6, 2026

Copy link
Copy Markdown

Upwind Upwind IaC Scan - ✅ Proceed with Deployment

0 misconfigurations detected

No default-branch baseline yet — showing all findings.

View full analysis in Upwind Console →

Scan completed in 1s

Scan history (2 scans)
Commit Scanned at New Resolved Net
84ab536 2026-08-06 10:52 UTC
84ab536 < 2026-08-06 10:52 UTC 0 0 0

Last scanned: 84ab536 · 2026-08-06 10:52 UTC

@rjain-g2
rjain-g2 marked this pull request as ready for review August 6, 2026 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant