Allow skipping specific versions of upstream projects #323
Conversation
This file contains 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
thespad
changed the title
|
I am a bot, here are the test results for this PR:
|
|
I am a bot, here are the test results for this PR:
|
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:
Allows setting e..g.
SKIP_EXTERNAL_TRIGGER="lychee_master_v6.2.0"to skip just that version from external trigger checks.Will still always skip package checks because there's no external version logic in those so the var needs to be removed once the new release is available - but it means we don't have to keep checking upstream for the next version release to be able to build.
Benefits of this PR and context:
How Has This Been Tested?
Source / References: