[pnpm] Add security settings to pnpm-workspace.yaml#4929
Merged
Conversation
Adds workspace-level security/hygiene settings to align with renovatebot configuration and supply chain hardening practices (mui/mui-public#1273). - updateNotifier: false — suppress pnpm update noise in CI / local dev - blockExoticSubdeps: true — reject git/path/tarball URLs in transitive deps - minimumReleaseAge: 4320 — 3 days, mirroring `security:minimumReleaseAgeNpm` used in renovate. minimumReleaseAgeExclude carves out our own published scope so we can pick up freshly-published @base-ui/* and @mui/internal-* bumps without waiting - trustPolicy: no-downgrade with trustPolicyIgnoreAfter: 525600 (365 days) to skip the trust check for legacy packages (semver@6.x via @babel/core, reselect@5.1.1, @octokit/*) that dropped provenance for specific releases. Tracked for removal in a TODO comment in pnpm-workspace.yaml.
commit: |
Bundle size
PerformanceTotal duration: 1,147.87 ms -43.50 ms(-3.7%) | Renders: 50 (+0) | Paint: 1,741.90 ms -80.42 ms(-4.4%)
11 tests within noise — details Check out the code infra dashboard for more information about this PR. |
✅ Deploy Preview for base-ui ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced May 27, 2026
Janpot
added
the
scope: code-infra
Janpot
requested review from
atomiks,
flaviendelangle and
michaldudak
as code owners
12 tasks
brijeshb42
approved these changes
May 28, 2026
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds pnpm workspace-level security/hygiene settings to align with renovatebot configuration and supply chain hardening practices. Same change shipped in mui/mui-public#1319 for the tracking issue.
Changes (
pnpm-workspace.yamlonly)updateNotifier: false— suppresses pnpm update noise in CI and local devblockExoticSubdeps: true— rejects git/path/tarball URLs in transitive dependenciesminimumReleaseAge: 4320— 4320 minutes (= 3 days), mirrors thesecurity:minimumReleaseAgeNpmrenovatebot preset already in use;minimumReleaseAgeExcludecarves out@base-ui/*(our own scope) and@mui/internal-*(our shared tooling) so we can pick up fresh internal bumps without waitingtrustPolicy: no-downgradepaired withtrustPolicyIgnoreAfter: 525600(365 days) — skips trust checks for packages published more than a year ago, avoiding false positives from widely-used packages (e.g.semver@6.3.1via@babel/core@7.x,reselect@5.1.1, parts of@octokit/*) that dropped provenance for specific releases. There is a TODO in the file to drop this once upstreams restore provenance /@babel/corestops depending onsemver@^6.3.1.No
overrides:were introduced — the trust-downgrade workaround is the policy-onlytrustPolicyIgnoreAfter, which doesn't change resolved versions and therefore doesn't affect what end users install.Verified locally:
pnpm install,pnpm dedupe --check,pnpm typescriptall clean.