fix: respect disabled pnpm release age by minimumReleaseAge: 0#278
Open
elecmonkey wants to merge 2 commits into
Open
fix: respect disabled pnpm release age by minimumReleaseAge: 0#278elecmonkey wants to merge 2 commits into
minimumReleaseAge: 0#278elecmonkey wants to merge 2 commits into
Conversation
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
1 participant
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.
🧭 Context
pnpm v11 enables
minimumReleaseAgeas 1 day by default, but users can explicitly disable it withminimumReleaseAge: 0.taze already detects pnpm v11 and applies the default maturity period, but it treated
minimumReleaseAge: 0as if the setting was absent. As a result, taze could be more restrictive than pnpm and skip valid updates that pnpm itself would install.📚 Description
This PR fix the problem above.