Adopt the release-tools automation - #117
Merged
Merged
Conversation
lorisleiva
force-pushed
the
feat/adopt-release-tools
branch
from
August 28, 2026 13:56
02c9a50 to
1cc8ca4
Compare
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.
This PR adopts codama-idl/release-tools
v1per RELEASING.md:postversionguard chains afterchangeset versioninrelease:version, blocking release PRs that cross a major illegally;release:publishscript, so the promote workflow has a package.json script to retag (the workflow'spublish-scriptnow points at it);cutandpromotedispatch wrappers calling the reusable workflows at@v1— withtracking-issueandannouncedefaulting to true, since spec is the repo that drives ecosystem transitions and hosts the announcement channel.Ported to
mainin a sibling PR.