Cuts the next minor release of Prisma Composer: bumps the root package.json version, propagates it to every workspace package in lockstep, and opens a PR titled "chore(release): v<next-version>". When a maintainer merges the PR, the `Publish to npm` workflow runs automatically and ships the new version to npm under dist-tag `latest`, plus a matching GitHub Release with auto-generated notes. Use when a maintainer asks to "cut the next minor", "bump to the next version", "open a release PR", or "prepare a publish PR".
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Maintainers who can push branches and open PRs. Invoke this locally, not as a
GitHub Action — a PR opened by a workflow's GITHUB_TOKEN does not trigger CI,
which defeats the point of a reviewable release.
Read docs/oss/versioning.md first — it is the
policy this skill mechanises: the root-package.json source of truth, the
lockstep guarantee, the dist-tag convention, and the full procedure (this skill
is the "open the bump PR" step; merging the PR is the publish trigger — there
is no separate dispatch step).
Confirm you can fetch from origin (git fetch origin main succeeds). The skill
works in a fresh worktree off origin/main, so your current worktree is left
undisturbed.
origin/main:
git fetch origin main
git worktree add -b chore/release-vNEXT ../release-vNEXT origin/main
cd ../release-vNEXT
pnpm install --frozen-lockfile
pnpm bump-minor reads the root version at HEAD, computes the next
minor (0.2.0 → 0.3.0), stamps every workspace package.json in
lockstep (rewriting internal workspace: deps to the new version), and
regenerates pnpm-lock.yaml to match.pnpm-lock.yaml — CI installs with --frozen-lockfile, so a bump without the
lockfile fails every CI job at the install step:
git diff --stat # every workspace package.json + pnpm-lock.yaml
pnpm check:publish-deps # no workspace:/catalog: leaks, exact internal pins
git commit -am "chore(release): v<version>"
git push -u origin chore/release-vNEXT
gh pr create --base main --title "chore(release): v<version>" \
--body "Release v<version>. Merging this triggers the Publish to npm workflow."
<version> to npm under latest (via OIDC trusted publishing) and cuts a
GitHub Release with auto-generated notes. Do not merge it yourself unless asked.Publish to npm workflow, triggered by the
merge — never run pnpm publish by hand for a normal release.gh release create --generate-notes) by the workflow; there is no committed
release-notes file to write.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.
The English summary is being prepared. Showing the original description.
Use when deploying or managing an app that uses Prisma Composer (`@prisma/composer`): wiring its services and Modules, running it locally, testing composed services, or standing up / tearing down an environment. Triggers on "prisma composer", "@prisma/composer", "prisma app", `prisma deploy`, `prisma dev`, `compute()`, `module()`, `contract()`, `service.load()`, `mockService`, `bootstrapService`.
The English summary is being prepared. Showing the original description.
How to upgrade `alchemy` and the `effect` constellation across this repo and keep them consistent for consumers: which packages pin what, why `effect` and every `@effect/*` companion move as one set, what breaks in a typical upgrade, and how to verify a standalone `npm install` still resolves a single `effect`. Use when asked to upgrade or bump alchemy or effect, when a deploy dies inside an alchemy provider with a `TypeError` naming a missing combinator, when `check:npm-effect-resolution` fails, or when deciding whether the alchemy patch is still needed.
The English summary is being prepared. Showing the original description.