Add release automation with npm trusted publishing#361
Open
david-crespo wants to merge 4 commits into
Open
Conversation
david-crespo
force-pushed
the
npm-trusted-publish
branch
from
July 4, 2026 22:52
781189f to
b957b97
Compare
Collaborator
Author
|
Might want to do staged publishing with manual final publish as an extra layer of security. |
david-crespo
added a commit
that referenced
this pull request
Jul 17, 2026
Won't publish by hand. Merging #361 will publish it. Bumps `@oxide/api` to `0.8.0`, tracking omicron release tag [`rel/v21/rc1`](https://github.com/oxidecomputer/omicron/releases/tag/rel/v21/rc1) (commit `3e5bafe`). - Update `OMICRON_VERSION` to the `rel/v21/rc1` commit SHA - Bump `@oxide/api` version `0.7.1` → `0.8.0` - Regenerate API client from the new spec - Update `oxide-openapi-gen-ts` test snapshots - Add system 21 row to the README versions table
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.
Automatic publish of both the generator and the client on main merge if the version in
package.jsonis not already published. So to publish either libraries, just merge a version bump to main. Canaries are not automatic on PR push, but can be manually triggered by going to the actions tab of the repo and entering the PR number. Instructions in README.