Skip to content

Renovate and various package manager min age unaligned #1816

Description

@MikeMcC399

Current behavior

The renovate.json configuration includes:

    "minimumReleaseAge": "7 days",
    {
      "matchPackageNames": ["cypress"],
      "minimumReleaseAge": "0 days"
    }

Package manager settings in the repo are not set up with aligned entries. This means that a local update may introduce dependencies that do not meet the minimumReleaseAge

Desired behavior

Using package managers locally should not install dependencies that conflict with Renovate rules.

Suggestion

Add or modify corresponding settings depending on the package manager involved.

npm is used in the root of the repo and in multiple examples directories. pnpm, Yarn v1 Classic and Yarn Modern are used in examples only.

npm

npm is not yet set up.

pnpm

pnpm examples are set up with minimumReleaseAge of 4320 in minutes. This is equivalent to 3 days.

An exception for cypress is in place using minimumreleaseageexclude.

Yarn v1 Classic

There is no provision in Yarn v1 Classic for a minimum release age.

Yarn v1 Classic pre-dates the supply chain attacks that have prompted minimum release age protection. Yarn v1 Classic in itself is unsupported since 2020. The action however continues to allow its use.

Yarn Modern

Yarn Modern examples are set up with npmMinimalAgeGate set to 3d (3 days).

An exception for cypress is in place using npmPreapprovedPackages.

Status

Set minimum age to 7 days in package managers:

  • npm
  • pnpm
  • Yarn Classic - no functionality available for this. The Yarn v1 Classic repo is frozen and no longer maintained
  • Yarn Modern

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions