Skip to content

Fix release Changeset and document npm bootstrap #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bjacobso merged 1 commit into from
Sep 25, 2026
Merged

Fix release Changeset and document npm bootstrap #31

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .changeset/public-custom-runtimes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,6 @@
"@triplex-build/triplex-sql": minor
"@triplex-build/triplex-sqlite": patch
"@triplex-build/triplex-postgres": patch
"@triplex-build/triplex-cloudflare": minor
"@triplex-build/triplex-testkit": minor
---

Expand Down
11 changes: 11 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,3 +40,14 @@ Add a Changeset for a publishable package change. Packages are not yet published
release must also validate a registry-only canary in a clean external consumer and retain the
existing PostgreSQL integration gate in CI. Current maturity and release gates live in
[`docs/current-state.md`](docs/current-state.md).

The first npm release needs a short-lived granular npm token with read/write publish access to the
`@triplex-build` scope and bypass 2FA enabled for unattended publishing. Organization-management
access is not needed. Add it as the `NPM_TOKEN` secret on the `npm-publish` GitHub environment before
approving the release job. After the packages exist, configure a trusted publisher on each npm
package for GitHub owner `bjacobso`, repository `triplex`, workflow `release.yml`, and environment
`npm-publish`, with direct publishing allowed. Then remove the bootstrap token. The workflow already
grants `id-token: write` and uses an OIDC-capable npm CLI for subsequent releases.

Keep private packages out of Changeset frontmatter. Changesets cannot version a public release
when a Changeset mixes private and publishable packages.
Loading