Repository navigation
Conversation
chore(release): promote v0.1.15 to main
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
1 participant
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.
Merge the official v0.1.15 promotion history from main back into dev while preserving merge ancestry. The branch trees are identical; this synchronization changes history only and keeps subsequent development based on the published release.
Verification: development, promotion, main and synchronization CI passed. The official release workflow passed on the main promotion commit; the published v0.1.15 tag and exact asset set were verified, and all four manifest checksums match GitHub asset SHA-256 digests. The branch trees match before synchronization. Merge with a merge commit after this PR's CI passes.