Skip to content

Adopt the shared release workflow with Trusted Publishing - #1155

Merged
lorisleiva merged 1 commit into
mainfrom
09-14-adopt_the_shared_release_workflow_with_trusted_publishing
Sep 14, 2026
Merged

lorisleiva merged 1 commit into
mainfrom
09-14-adopt_the_shared_release_workflow_with_trusted_publishing

Conversation

@lorisleiva

Copy link
Copy Markdown
Member

This PR replaces the inline release job with a call to the shared workflow from codama-idl/release-tools (v1.3.1), which publishes to npm via Trusted Publishing (OIDC). NPM_TOKEN is no longer referenced; id-token: write is granted on the caller as npm requires. publish-packages becomes release:publish and the release-tools dependency is bumped to v1.3.1 for the trust-publishers command.

Proven on the renderers-rust-cpi canary (codama-idl/renderers-rust-cpi#118@codama/renderers-rust-cpi@0.1.4 published with SLSA provenance). Before merging #1119, run pnpm exec release-tools trust-publishers once from this repository: it configures all 17 public packages (including the freshly bootstrapped @codama/upgrade).

The release PR #1119 is retitled to [1.x] Release package by the next release run; it stays attached (the changesets action matches it by head branch).

This PR replaces the inline release job with a call to the shared workflow from codama-idl/release-tools (v1.3.1), which publishes to npm via Trusted Publishing (OIDC). `NPM_TOKEN` is no longer referenced; `id-token: write` is granted on the caller as npm requires. `publish-packages` becomes `release:publish` and the release-tools dependency is bumped to `v1.3.1` for the `trust-publishers` command.

Proven on the renderers-rust-cpi canary (codama-idl/renderers-rust-cpi#118 → `@codama/renderers-rust-cpi@0.1.4` published with SLSA provenance). Before merging #1119, run `pnpm exec release-tools trust-publishers` once from this repository: it configures all 17 public packages (including the freshly bootstrapped `@codama/upgrade`).

The release PR #1119 is retitled to `[1.x] Release package` by the next release run; it stays attached (the changesets action matches it by head branch).
@changeset-bot

changeset-bot Bot commented Sep 14, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: a103d84

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 September 14, 2026 15:30

Copy link
Copy Markdown
Member Author

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

@lorisleiva
lorisleiva merged commit 393e9c7 into main Sep 14, 2026
5 checks passed
@lorisleiva
lorisleiva deleted the 09-14-adopt_the_shared_release_workflow_with_trusted_publishing branch September 14, 2026 16:09
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