chore(release): 0.1.29 - #144
Merged
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.com>
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
## [0.1.29] - 2026-09-28.0.1.28tag is an unsignedlightweight ref with no promotion record, so the promotion gate correctly
refused it and release-tag immutability forbids updating it in place.
git tag -s 0.1.29 -F promotion.jsoncarrying the
nddev-public-release-promotion/v2record bound to thismerge commit's push evidence (ci run, static validators job, security run).
Validation
validate_all --tier releaseon the release branch: all checks passexcept
release-ledger-tags, which needs the tag ref created after merge.Test plan
ci,static validators, and a securityrun on the merge commit.
publish and verify five checksummed assets.