feat(git): allow version policy functions#2152
Open
ramboman wants to merge 2 commits intofolke:mainfrom
Open
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
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.
Description
With this pull request, it is possible to assign a function to the
versionkey in the configuration or in a spec to implement more complex version policies.Examples of problems it can solve
Example 1
The user want
lazy.nvimto respect a cooldown period (e.g.: 21 days) for all packages. It is part of his strategy to mitigate the threat of supply chain attacks. Here is a simple way to achieve this:Add this function somewhere in the personal configuration files:
Note: Inspired by #2135
Assign to the
defaultsversionkey the following version policy function:Example 2
The user has a more complex version policy for a specific plugin. He wants:
Here is a way to achieve this:
Add these functions somewhere in the personal configuration files:
Assign to the
specversionkey the following version policy function:Related Issue(s)
Screenshots