Repository navigation
Follow the products' released versions: @prisma/orm-toolchain 8.0.0-rc.21 -> 8.0.0-rc.22 - #381
Merged
Merged
Conversation
…c.21 -> 8.0.0-rc.22 Opened automatically (update-product-versions.yml); merging ships a dev version of the CLI. A real release stays a human act. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
prisma-bot
enabled auto-merge (squash)
October 31, 2026 06:23
|
No actionable comments were generated in the recent review.
 |
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title clearly identifies the dependency and the exact version update from 8.0.0-rc.21 to 8.0.0-rc.22. |
| Description check | |
The description accurately explains the automated version update and its release-related purpose. |
| Docstring Coverage | |
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
Simplify code
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
commit: |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
This was referenced Nov 2, 2026
Merged
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.
Opened automatically by update-product-versions.yml, following the products' release dist-tags (@prisma/orm-toolchain 8.0.0-rc.21 -> 8.0.0-rc.22). Merging publishes a
devversion of the CLI; the conformance checks on this pull request are what stand between a product release and that dev build.