feat: add min-release-age-exclude config#9534
Merged
Merged
Conversation
Co-authored-by: Casey Holzer <casey.h@leantaas.com> (cherry picked from commit c3e1a71)
owlstronaut
approved these changes
Jun 10, 2026
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.
Manual backport of #9532 to
release/v11.min-release-age-excludeexempts packages (exact name or glob, e.g.@myorg/*) from themin-release-age/beforepublish-time filter. Applied in install, update, outdated, and query.Cherry-picked from c3e1a71 (
-x). Two differences from the original PR:strict-allow-scriptsdescription and smoke snapshot are already in sync, so there was no drift to fix.Ref #8994, #9532.