Repository navigation
fix: publish fragments with deploy-kit 0.19.2, which knows the substrate's image pull - #145
Merged
Merged
Conversation
…ate's image pull The 0.20.1 release could not publish the Platform document: Publish Fragment v0.28.0 validates with deploy-kit 0.19.0, which refuses substrate.imagePull. v0.29.0 validates with 0.19.2 (JorisJonkers-dev/github-workflows#172).
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.
Summary
The 0.20.1 release could not publish the Platform document. Publish Fragment v0.28.0 validates with deploy-kit 0.19.0, which refuses
substrate.imagePull("imagePull" is not a field of the model). Every other fragment published. Release now calls Publish Fragment v0.29.0, which validates with deploy-kit 0.19.2 (JorisJonkers-dev/github-workflows#172), so the next release publishes the Platform document with the five-minute image pull from #144.Testing
platform.intent.ymlwith the node contract and the images lock. The only refusals are the cross-repository references this repository cannot resolve on its own.