Skip to content

docs(versioning): bootstrap section reflects the two-package surface #62

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
wmadden merged 1 commit into from
Jul 13, 2026
Merged

docs(versioning): bootstrap section reflects the two-package surface #62

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
17 changes: 10 additions & 7 deletions docs/oss/versioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,15 +118,18 @@ cannot publish the initial version of a package via OIDC** — the package must
exist before you can enable a trusted publisher (unlike PyPI). So the first release is a
one-time manual bootstrap; every release after that goes through the workflow:

1. **Create the packages once, with a token.** On a machine logged in to npm as a user
with publish rights to the `@prisma` scope (and the ability to create the unscoped
`prisma-compose`): `pnpm install && pnpm build`, then
`node scripts/publish-packages.mjs --tag latest`. This publishes all nine packages at
the current root version with correct exact-pinned deps.
2. **Configure a trusted publisher on each of the nine packages** at
_Completed 2026-07-12 for both packages; kept as the procedure for any future
package (e.g. a new `@prisma/compose-<target>`)._

1. **Create the package once, with a token.** On a machine logged in to npm as a
user with publish rights to the `@prisma` scope: `pnpm install && pnpm build`,
then `node scripts/publish-packages.mjs --tag latest`. This publishes the
publishable packages (the two in `packages/9-public/`) at the current root
version with correct exact-pinned deps.
2. **Configure a trusted publisher on each published package** at
`npmjs.com/package/<name>/access` → *Trusted Publisher* → GitHub Actions:
- Organization or user: `prisma`
- Repository: `app`
- Repository: `compose`
- Workflow filename: `publish.yml`
- Environment: leave blank
- Allowed action: **npm publish**
Expand Down
Loading