Skip to content

chore: add pnpm minimumReleaseAge protection (7 days)#42

Open
matthew-douville wants to merge 1 commit into
mainfrom
pnpm/minimum-age
Open

chore: add pnpm minimumReleaseAge protection (7 days)#42
matthew-douville wants to merge 1 commit into
mainfrom
pnpm/minimum-age

Conversation

@matthew-douville

Copy link
Copy Markdown
Contributor

Summary

  • Adds minimumReleaseAge: 10080 (7 days) and minimumReleaseAgeExclude for @layerzerolabs/* and @stargatefinance/* to the pnpm block in package.json.
  • Mirrors the policy already in place in offchain-monorepo so newly published versions of third-party packages can't land in this repo for at least a week (mitigation against fast-moving supply-chain compromises).
  • Internal scopes are excluded so our own releases aren't gated by the delay.

Notes

  • pnpm 10.17 (already pinned via packageManager) supports this setting.
  • The constraint only applies on pnpm install / pnpm update; the existing pnpm-lock.yaml is unaffected until the next resolution.

Test plan

  • pnpm install succeeds and does not attempt to fetch any third-party packages younger than 7 days
  • pnpm update (dry-run / sandbox) skips out-of-window upgrades for non-excluded scopes
  • @layerzerolabs/* and @stargatefinance/* packages still resolve normally

Mirrors the policy in offchain-monorepo: blocks installing dependency
versions younger than 7 days, with @layerzerolabs/* and @stargatefinance/*
excluded so internal releases aren't gated.
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