Skip to content

Adopt the release-tools automation - #1124

Merged
lorisleiva merged 1 commit into
mainfrom
08-28-adopt_the_release-tools_automation
Aug 28, 2026
Merged

Adopt the release-tools automation#1124
lorisleiva merged 1 commit into
mainfrom
08-28-adopt_the_release-tools_automation

Conversation

@lorisleiva

Copy link
Copy Markdown
Member

This PR adopts codama-idl/release-tools v1.0.0 per RELEASING.md: the postversion guard chains after changeset version (blocking illegal major crossings and same-major-invariant violations in release PRs), and the cut/promote dispatch wrappers call the reusable workflows at @v1. Note: the guard will pass on the regenerated release PR because changeset version takes all public packages to major 1 (#1100's promotions); the current unversioned tree intentionally fails it until #1119 merges.

@changeset-bot

changeset-bot Bot commented Aug 28, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 17ef8e6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@lorisleiva
lorisleiva marked this pull request as ready for review August 28, 2026 12:56

Copy link
Copy Markdown
Member Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

This PR adopts [codama-idl/release-tools](https://github.com/codama-idl/release-tools) `v1.0.0` per [RELEASING.md](https://github.com/codama-idl/spec/blob/HEAD/RELEASING.md): the `postversion` guard chains after `changeset version` (blocking illegal major crossings and same-major-invariant violations in release PRs), and the `cut`/`promote` dispatch wrappers call the reusable workflows at `@v1`. Note: the guard will pass on the regenerated release PR because `changeset version` takes all public packages to major 1 (#1100's promotions); the current unversioned tree intentionally fails it until #1119 merges.
@lorisleiva
lorisleiva force-pushed the 08-28-adopt_the_release-tools_automation branch from 4c0153b to 17ef8e6 Compare August 28, 2026 14:40
@lorisleiva
lorisleiva merged commit 2437f5e into main Aug 28, 2026
5 checks passed
@lorisleiva
lorisleiva deleted the 08-28-adopt_the_release-tools_automation branch August 28, 2026 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant