Repository navigation
Bump to version 8.0.0-rc.30 - #380
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
|
Warning Review limit reachedThis review ran on the open-source allowance, not this organization's plan, because the pull request author doesn't have an assigned seat. Waiting won't change this — ask an organization admin to assign them a seat, or add seats in Billing if every seat is already assigned, then retry. Next included review available in 48 minutes. View limit details
Comment |
commit: |
wmadden
approved these changes
Nov 3, 2026
This was referenced Nov 3, 2026
wmadden
pushed a commit
that referenced
this pull request
Nov 6, 2026
Merging this PR publishes `prisma@8.0.0-rc.31` and `@prisma/cli@8.0.0-rc.31` under `latest`. It is the first release that carries Composer 0.37.0: ```console $ npm view prisma@8.0.0-rc.31 dependencies '@prisma/composer-cli': '0.37.0' ``` The main user benefit of Composer 0.37.0 is a much smaller install: 1.6 GB down to 473 MB. ## What changes - **Version bump 8.0.0-rc.30 → 8.0.0-rc.31**, made by `pnpm bump-version` (the `publish-npm-version` skill). The same files change as in #380. `@prisma/compute` keeps its own version; only its `workspace:` dependency on `@repo/tsconfig` moves. - **The Composer pins** moved to 0.37.0 in #385, which prisma-bot opened and merged. That commit's CI on `main` passed, including the real-API end-to-end suite. - **`docs/reference/error-reference.md` gets a `CONFIG` section.** Composer 0.37.0 adds three codes: `CONFIG.ADAPTER_FAILED`, `CONFIG.ADAPTER_INVALID` and `CONFIG.SECRET_AS_PLAIN_VALUE`. The page had no `CONFIG` section at all, so the ten older `CONFIG.*` codes Composer raises were missing too. The section lists all 13, written from the 0.37.0 package source. The page says family codes are kept current by hand when the CLI moves to a new family release, which is why this rides in the release PR. ## What merging does The squashed push to `main` changes the root version. The `Publish to npm` workflow then publishes `@prisma/cli-engine` and `@prisma/cli`, and creates a GitHub Release with generated notes (marked pre-release on the RC line). See [`docs/oss/versioning.md`](../blob/main/docs/oss/versioning.md). Agent: dumbo-83 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
wmadden
pushed a commit
that referenced
this pull request
Nov 6, 2026
…pins an older ORM toolchain (#384) When a product publishes a release, the version-follow pull request now releases the CLI too: ```text Release 8.0.0-rc.31: follow the products' released versions: @prisma/orm-toolchain 8.0.0-rc.22 -> 8.0.0-rc.23 ``` `update-product-versions.yml` moves the pins as before, then runs `pnpm bump-version`. When the pull request passes its checks and merges, the root version changes, so `publish.yml` publishes the release under `latest`. No person needs to cut it. ## Why `prisma@8.0.0-rc.29` pinned `@prisma/orm-toolchain` 8.0.0-rc.21 for four days after ORM rc.22 shipped. A project on ORM rc.22 installed two toolchains, and the CLI ran the old one ([reported on Discord](https://discord.com/channels/937751382725886062/1477940100561244295/1566776463729102999)). - The follow pull request #381 merged on 2026-10-31, but it shipped only a dev build. - The release pull request #380 waited four days for a review. The same thing happened with rc.21 in October. A CLI behind a product release breaks every project on that release, so the release should not wait for someone to remember it. ## What changes 1. **The follow pull request bumps the version.** It runs `pnpm bump-version` and stages every file it changes: the workspace manifests, the lockfile and the version stamp in `skills/prisma-platform-core-concepts/SKILL.md`. The title starts with `Release <version>:`. 2. **Open release pull requests are closed as superseded.** A `Bump to version` pull request would race the same version number. Older follow pull requests are closed as before. 3. **Pins on `main` that no release shipped are released.** Suppose a maintainer's release merges first and takes the version number. Then the follow pull request's squash changes no version and ships only a dev build, and the registry comparison finds nothing left to move. So on the release channel, `update-product-versions.mjs` now compares `main`'s pins with the manifests at the last release's tag, `v<version>`. The next run, or the daily run at the latest, opens a release for those pins. The checkout fetches tags for this. 4. **`bump-version` passes `--no-frozen-lockfile`**, because pnpm defaults to a frozen lockfile in CI. A release for a change in this repository alone is still cut by a maintainer. `docs/oss/release-automation.md`, `docs/oss/versioning.md` and the README now say this. They also say the merge still needs the one approving review the `main` ruleset requires, which CodeRabbit gives today. ## How it was checked - `pnpm bump-version` with `CI=true` moved rc.30 to rc.31 and changed exactly those files. `git add -u` stages exactly them. - New tests for `pinChanges`, and `pnpm test:scripts` passes (89 tests). `actionlint` and `pnpm lint` pass. - Against the real registry: on `main` today, the release channel reports no change. With the root version set back to rc.29, it reports the three pins rc.30 shipped. ## Alternatives considered - **Keep releases manual, and open the release pull request automatically for a person to approve.** This removes the step of remembering, but #380 shows an approval can wait for days. - **Only alert when `prisma@latest` falls behind.** The nightly getting-started check in prisma/getting-started-eval now does this, as a second line of defence. Alone, it reports the problem without fixing it. Related: prisma/orm#30944 makes the ORM's publish workflow notify this repository at once. It read a secret that was never set, so the follow pull request waited for the daily run. Refs TML-3439. Agent: uther-28 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
npx prisma devfails for every new Composer project today:This PR releases 8.0.0-rc.30, which fixes it. The fix is already on
main(#378); it has not been released.Why it fails
prisma8.0.0-rc.29 bundles Composer 0.35.0. Composer 0.36.0 came out yesterday, and the getting-started page'snpm install @prisma/composer @prisma/composer-prisma-cloudinstalls it. The CLI's 0.35.0 and the project's 0.36.0 disagree on the data they pass to each other, soprisma devstops before anything starts. #378 moves the CLI to Composer 0.36.0.What users see change
Composer 0.36.0 renames a stage to an environment:
prisma deploy --environment <name>replaces--stage.--stagenow fails withCLI.COMMAND_MOVED, naming the replacement.prisma dev,dev urlanddev stopalso take--environment, and each environment runs its own local copy.prisma devreads secrets from the environment and no longer invents placeholder values.The docs,
prisma/cloud-deploy-actionandcreate-prismafollow in their own PRs, after this release.How it was checked
prismapackage from Follow the products' released versions: @prisma/composer-cli 0.35.0 -> 0.36.0; @prisma/composer 0.35.0 -> 0.36.0 #378's branch and installed it with Composer 0.36.0 into the Composer getting-started app.prisma devreached ready, the gateway answered with a quote, and the direct call to the quotes service got the 401 the page expects.prisma deploy --stage xfailed withCLI.COMMAND_MOVED, naming--environment.Release
Previous version 8.0.0-rc.29, new version 8.0.0-rc.30. See docs/oss/versioning.md. Merging this PR ships the release: the push to
mainchanges the root version, thePublish to npmworkflow publishes@prisma/cli-engineand then@prisma/cliandprismaunderlatest, and creates a pre-release GitHub Release with generated notes.The diff touches the same files as the rc.29 release (#379).
Agent: janeway-45
🤖 Generated with Claude Code