Repository navigation
ci: publish the fragment with github-workflows v0.34.0 - #22
Merged
Merged
Conversation
Its deploy-kit 0.26.1 takes the images lock's version field, which v0.33.0's deploy-kit 0.25.0 refused, so this repository's last release pushed its images but no fragment (JorisJonkers-dev/github-workflows#187).
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.
The last release pushed its images but failed at the fragment step: github-workflows v0.33.0 validates with deploy-kit 0.25.0, which refuses the images lock's
versionfield. v0.34.0 pins deploy-kit 0.26.1, which takes it (JorisJonkers-dev/github-workflows#187). Once this merges, Publish is dispatched for the existing tag, and its fragment's lock is read back forversion(JorisJonkers-dev/workspace#141).