Repository navigation
ci: pin sborka actions to v0.5.0.130 - #33
Merged
Merged
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.
Pins every
youndie/sborkaaction and reusable workflow this repository calls from@mainto the release tagv0.5.0.130(youndie/sborka#123). With@main, a merge to sborka changed this repository's CI at once, with no pull request of its own and without this repository's build ever running on the change; with a tag, Renovate proposes each new sborka tag as a pull request (thegithub>youndie/sborkapreset carries the rule that reads the four-part tag), and that pull request runs this repository's build.v0.5.0.130is the first tag in whichpublish-wip.yamlalso takes its own inner actions from the same revision rather than from@main.Refs youndie/sborka#123