Skip to content

security: enforce 7-day minimum package age for pnpm installs #1198

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lindyalchemy wants to merge 1 commit into
base: main
Choose a base branch
from
Open

security: enforce 7-day minimum package age for pnpm installs #1198

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions pnpm-workspace.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
minimumReleaseAge: 10080
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Upgrade pnpm before enabling minimumReleaseAge

minimumReleaseAge is configured here, but this repo still runs pnpm 10.9.0 (package.json and .github/actions/setup-pnpm/action.yml both pin 10.9.0), while pnpm’s official settings docs mark minimumReleaseAge as “Added in: v10.16.0”. In current CI/local installs, this policy is therefore not actually enforced, so the commit creates a false sense of supply-chain protection until the pnpm version is bumped to one that supports the setting.

Useful? React with 👍 / 👎.

Loading