Index of every page on this site: llms.txt
All skills
prisma avatar

/publish-npm-version

@6914c1d
by prismaprisma/prisma-cli26 stars
4
Run it yourself

Cuts the next release of the unified Prisma CLI: bumps the root package.json version (on the Prisma 8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every lockstep workspace package, and opens a PR titled "chore(release): bump to <next-version>". When the maintainer merges the PR, the `Publish to npm` workflow ships @prisma/cli-engine and @prisma/cli under dist-tag `latest` (RC versions get a pre-release GitHub Release). 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".

Use this Skill: https://skilld.dev/gh/prisma/prisma-cli/publish-npm-version

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈149 tokens for metadata: the name and description. ≈1.1k when used: this file.

Description uses 7.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈596 characters, or 7.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Publish next npm version

Audience

Maintainers of the unified Prisma CLI with permission to push branches and open PRs in prisma/prisma-cli. The skill runs locally, never as a GitHub Action — a locally opened PR triggers CI normally, which is the point of a reviewable release PR.

Background reading

Read docs/oss/versioning.md first. It covers the source-of-truth model (root package.json version), the lockstep guarantee (@prisma/compute excluded by ruling), the Prisma 8 RC line, the dist-tag convention, and the release procedure this skill is one step of. One note specific to this repo: the lockstep excludes @prisma/compute by operator ruling.

Pre-flight

No requirement to be on main or have a clean tree — all work happens in a fresh worktree off origin/main. Confirm git fetch origin main succeeds; if not, stop and surface the issue.

Procedure

  1. Fetch and determine the target version.

    git fetch origin main
    CURRENT=$(git show origin/main:package.json | node -e 'process.stdout.write(JSON.parse(require("fs").readFileSync(0,"utf8")).version)')
    NEXT=$(node -e "import('./scripts/determine-version-utils.ts').then(m => process.stdout.write(m.computeNextReleaseVersion(process.argv[1])))" "$CURRENT")
    echo "$CURRENT → $NEXT"

    $NEXT names the branch and PR; step 3 recomputes the authoritative value inside the fresh worktree and the two must agree.

  2. Create a fresh worktree off origin/main.

    git worktree add -b "release/$NEXT" "../release-$NEXT" origin/main
    cd "../release-$NEXT"
  3. Bump. pnpm install --frozen-lockfile --ignore-scripts if the worktree has no node_modules, then pnpm bump-version. Confirm the version it wrote matches $NEXT; on mismatch the worktree's value is authoritative — remove worktree and branch, restart from step 1.

  4. Check the lockfile moved. pnpm bump-version refreshes pnpm-lock.yaml itself, because internal deps are pinned workspace:<version> and a stale lockfile fails every later frozen install with ERR_PNPM_OUTDATED_LOCKFILE. If it is missing from the diff, stop — the bump did not finish.

  5. Sanity-check the diff. Only package.json files and pnpm-lock.yaml; manifests change exactly version + workspace:<old> → workspace:<new>; the excluded packages/compute/package.json is untouched.

  6. Commit everything in one commit:

    chore(release): bump to <version>
  7. Push the branch to origin.

  8. Open the PR with gh pr create. Use the title:

    Bump to version <version>

    Body: previous → new version; link docs/oss/versioning.md; note that merging this PR ships the release — the squashed push to main changes the root version with the release marker, the Publish to npm workflow publishes @prisma/cli-engine then @prisma/cli under latest, and a GitHub Release (pre-release on the RC line) is created with generated notes. This repo has no committed release-notes file gate; review the generated notes on the Release after merge.

  9. Stop and report the PR URL and the worktree path. Do not merge — the merge is the human gate that triggers the publish. The maintainer removes the worktree after merge (git worktree remove ../release-<version>).

Idempotency

pnpm bump-version reads the root version from git show HEAD:package.json, so re-running in the same worktree cannot double-bump. The skill as a whole is not idempotent: step 2 fails if the branch/worktree already exist — remove them (git worktree remove ../release-$NEXT; git branch -D release/$NEXT) or continue inside the existing worktree from step 3. Do not stack bumps.

Out of scope

  • Merging the PR (human gate; merging is the publish trigger).
  • Patch releases. On the RC line a fix is just the next rc.N.
  • Beta tags — hand-cut via workflow_dispatch of Publish to npm with the beta dist-tag; this skill always advances the release version.
  • @prisma/compute — excluded from the lockstep by operator ruling (2026-08-10); it versions and publishes independently (publish-compute.yml) pending extraction to another repo.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    The skill automates the npm release process for the Prisma CLI. It handles version bumping, branch management via git worktrees, and PR submission using standard development tools like git, node, and pnpm. All operations are confined to the local repository and official Prisma release workflows.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at 6914c1d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 3 months ago

README badge

README badge for prisma/prisma-cli/publish-npm-version