Skip to content

fix: publish fragments with deploy-kit 0.19.2, which knows the substrate's image pull - #145

Merged
ExtraToast merged 1 commit into
mainfrom
fix/publish-with-deploy-kit-0.19.2
Oct 18, 2026
Merged

ExtraToast merged 1 commit into
mainfrom
fix/publish-with-deploy-kit-0.19.2

Conversation

@ExtraToast

Copy link
Copy Markdown
Contributor

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

  • deploy-kit 0.19.2 validates platform.intent.yml with the node contract and the images lock. The only refusals are the cross-repository references this repository cannot resolve on its own.

…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).
@ExtraToast ExtraToast added type: bug Something is broken or behaving incorrectly. component: ci Continuous integration workflow or check behavior. labels Oct 18, 2026
@ExtraToast ExtraToast self-assigned this Oct 18, 2026
@ExtraToast
ExtraToast merged commit 5df430f into main Oct 18, 2026
@ExtraToast
ExtraToast deleted the fix/publish-with-deploy-kit-0.19.2 branch October 18, 2026 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component: ci Continuous integration workflow or check behavior. type: bug Something is broken or behaving incorrectly.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant