Skip to content

chore: add min-release-age cooldown to .npmrc#3286

Open
nkaradzhov wants to merge 1 commit into
redis:masterfrom
nkaradzhov:min-release-age
Open

chore: add min-release-age cooldown to .npmrc#3286
nkaradzhov wants to merge 1 commit into
redis:masterfrom
nkaradzhov:min-release-age

Conversation

@nkaradzhov
Copy link
Copy Markdown
Collaborator

@nkaradzhov nkaradzhov commented May 20, 2026

Set a 1-day cooldown on new dependency versions as a low-cost defense against supply-chain attacks. Requires npm CLI 11.10.0+.

Description

Describe your pull request here


Checklist

  • Does npm test pass with this change (including linting)?
  • Is the new or changed code fully tested?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

Note

Low Risk
Low risk config-only change that affects how npm resolves/installs newly released package versions; potential impact is slower uptake of fresh releases in CI/developer installs.

Overview
Adds an .npmrc setting min-release-age=1 to enforce a 1-day delay before newly published dependency versions are eligible for install, as a supply-chain hardening measure.

Reviewed by Cursor Bugbot for commit 0cc797d. Bugbot is set up for automated code reviews on this repo. Configure here.

Set a 1-day cooldown on new dependency versions as a low-cost
defense against supply-chain attacks. Requires npm CLI 11.10.0+.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@PavelPashov PavelPashov left a comment

Choose a reason for hiding this comment

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

Do we need to make sure that we have the correct version in the release workflow?

- name: Use npm with min-release-age support
  shell: bash
  run: npm install -g npm@^11.10.0

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.

2 participants