feat: Support for minimum release age#69
Open
abstractalgo wants to merge 1 commit into
Open
Conversation
abstractalgo
force-pushed
the
feat-min-release-age
branch
from
0828005 to
afc1c4c
Compare
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.
This adds a support for minimum release age as a config (instead of reading directly from any of the package manager configs).
Adds two configs:
"minimumReleaseAge": Mirrors npm's minimumReleaseAge. Hide upgrades to versions published less than this many minutes ago. When the newest version is held back, the decoration shows the highest eligible upgrade and the true latest (e.g.5.1.0 (latest 5.2.0))."minimumReleaseAgeExclude": Package names to exclude from the minimumReleaseAge check.Example of how it looks: