Skip to content

chore:[] harden dependency installation - #3361

Open
contentful-supply-chain-migrator[bot] wants to merge 1 commit into
mainfrom
repo-migrator/supply-chain-controls
Open

contentful-supply-chain-migrator[bot] wants to merge 1 commit into
mainfrom
repo-migrator/supply-chain-controls

Conversation

@contentful-supply-chain-migrator

Copy link
Copy Markdown

hold new dependency releases for 2 days

This repository fails the dependency-release-age governance control. This PR makes the one change below.

What changed

hold new dependency releases for 2 days

  • Package manager: npm
  • Edits: .npmrc
  • Before: not set
  • After: min-release-age=2

Not changed

  • ignore-scripts: already-compliant. .npmrc disables dependency lifecycle scripts.

Read before merging

  • The control still reports a finding that does not block a merge: min-release-age needs npm 11.10.0 or newer to take effect, and Node 24 with no patch version, so the npm it resolves to is unsettled (npm 11.10.0 needs Node 24.14.1 or newer), so the cooldown cannot be confirmed to apply. Pin a full Node version in .node-version, or set engines.npm alongside engine-strict=true.

Verification

The dependency-release-age control still reports a finding that does not block a merge; see Read before merging. Checked against the control's own code at 1dec3b1b on main.

Why

The RAPID: Supply Chain Controls adds this control. See Dependency Release Age Control for the per-manager details.

Review

  • Created by the supply-chain migration and labeled supply-chain-rollout. If it is still a draft, mark it ready for review when you want your code owners requested.
  • Merge it through your normal review process. It is not merged automatically.
  • The setting only takes effect on a package manager version that supports it. Where the repository does not pin one, this PR still adds the setting and says so under Read before merging. Repositories where no edit would help are skipped.

Something is broken

Please reach out to the Product Security team, or look at the code that created this PR, and we can work out how to make it migrate every repository correctly.

Package manager: npm
Edits: .npmrc
Before: (not set)
After: min-release-age=2
Note: The control still reports a finding that does not block a merge: min-release-age needs npm 11.10.0 or newer to take effect, and Node 24 with no patch version, so the npm it resolves to is unsettled (npm 11.10.0 needs Node 24.14.1 or newer), so the cooldown cannot be confirmed to apply. Pin a full Node version in .node-version, or set engines.npm alongside engine-strict=true.

Control: Dependency Release Age Control (https://contentful.atlassian.net/wiki/spaces/SRT/pages/7107936363)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants