Repository navigation
ci: publish fragments with deploy-kit 1.0 - #21
Merged
Merged
Conversation
Publish Fragment v0.36.0 validates and packs with deploy-kit 1.0.0, which the estate composes with. v0.35.0's deploy-kit 0.28 refuses the 1.0 fragments it validates beside, so a release on it does not publish (estate-dashboard 0.9.1, 2026-10-27).
ExtraToast
added
the
type: chore
ExtraToast
enabled auto-merge (squash)
October 27, 2026 20:06
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
Publish Fragment moves from an older pin to v0.36.0 (
16d241e4), which validates and packs with deploy-kit 1.0.0, the toolkit the estate composes with.ci:. It takes effect on this repository's next release.Test plan
deploy/on main validated on deploy-kit 1.0.1, together with every other participant's (accepted)Part of JorisJonkers-dev/deploy-kit#380.