Publish Npm Version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC...
Install
npx skills add prisma/orm --skill publish-npm-version -g -a claude-code -y- Repository
- prisma/orm47.7k
- Category
- Git and review
- Updated
- 4d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to <next-version>". When the maintainer merges the PR, the `Publish to npm` workflow runs automatically and ships the new version to npm under the dist-tag its shape implies (`latest`; RC releases get a pre-release GitHub Release), plus a matching GitHub Release. Also prepares the matching prisma/web docs-site PR from the same release notes, to merge once the release is published. Use when a maintainer asks to "cut the next RC", "cut the next release", "bump to the next version", "open a release PR", or "prepare a publish PR".
Publish next npm version
Audience
Maintainers of Prisma 8 who have permission to push branches and open PRs in the repository. The skill is invoked locally by the maintainer; it does not run as a GitHub Action. Running locally is what makes the resulting PR trigger CI normally, PRs opened by a workflow's GITHUB_TOKEN do not, which defeats the point of cutting a reviewable release.
Background reading
Read docs/oss/versioning.md before running this skill. It covers:
- The source-of-truth model (root
package.jsonversion). - The lockstep guarantee (every workspace package matches the root).
- The v8 RC line (
8.0.0-rc.N, withlatesttracking the newest RC or stable release). - The dist-tag convention (
latest/dev/beta). - The full release procedure (this skill covers steps 1-2 of 3; merging the PR is the publish trigger, there is no separate dispatch step).
- The emergency-patch path (this skill does not handle patches).
This SKILL.md covers steps 1-2, opening the bump PR, assembling upgrade guides, and driving the release notes. Merging (step 3) stays the human gate. Read the canonical upgrade instruction lifecycle for fragment storage, synthesis, archives, and coverage-check modes.
Pre-flight
The skill does not require the maintainer to be on main or to have a clean working tree, it does all the work in a fresh worktree off origin/main, so the maintainer's current worktree (typically a feature branch in worktrees/<feature>/) is left undisturbed.
Before invoking this skill, confirm:
