[code-infra] Revert [email protected] minimumReleaseAge exemption#22953
Merged
Conversation
…de (mui#22923)" This reverts commit c92c2ff. The `minimumReleaseAgeExclude` entry for [email protected] was a temporary, self-expiring workaround. [email protected] (with restored SLSA provenance) has now aged past the 3-day `minimumReleaseAge` soak window and is the newest 3.3.x, so re-resolution (the react@^18 package-overrides install, `pnpm dedupe`) lands on it and passes `trustPolicy: no-downgrade` on its own merit. The exemption is inert, so remove it. Co-Authored-By: Claude Opus 4.8 <[email protected]>
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
LukasTy
added
type: enhancement
brijeshb42
approved these changes
Jun 25, 2026
mbrookes
pushed a commit
to mbrookes/mui-x
that referenced
this pull request
Jun 27, 2026
) Co-authored-by: Claude Opus 4.8 <[email protected]>
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.
Reverts the temporary workaround from #22923.
Why
[email protected](restored SLSA provenance) has now aged past the 3-dayminimumReleaseAgesoak window (it became installable at 2026-06-24 21:23 UTC) and is the newest3.3.x. So any re-resolution (thereact@^18package-overridesinstall,pnpm dedupe) now lands on3.3.15and passestrustPolicy: no-downgradeon its own merit. TheminimumReleaseAgeExcludeentry is inert and can be removed.Verification
A re-resolving install on the repo's exact policy settings +
[email protected], with no nanoid exemption, succeeds and resolves[email protected].Note: this self-heals only because nanoid's latest
3.3.xis attested. If the maintainer later ships another provenance-less patch, the sameERR_PNPM_TRUST_DOWNGRADEcan recur on the react_18 re-resolution and the one-line exemption (pointed at the next attested version) would be reintroduced.🤖 Generated with Claude Code