TML-3170: publish releases as 8.0.0-rc.N (latest tracks the RC line)

[wmadden-electric]

Linked issue

Refs TML-3170.

Follow-up (not in this PR): the release PR that bumps the root version 0.17.0 → 8.0.0-rc.1 via the publish-npm-version skill, which is what actually starts the RC line.

At a glance

// scripts/determine-version-utils.ts
export function computeNextReleaseVersion(current: string): string {
  assertCanonicalBase(current);
  const rcMatch = current.match(RC_BASE_PATTERN);
  if (rcMatch) {
    const [, major, minor, patch, rc] = rcMatch;
    return `${major}.${minor}.${patch}-rc.${Number(rc) + 1}`;
  }
  if (parseVersion(current).major < 8) {
    return '8.0.0-rc.1';
  }
  return computeNextMinor(current);
}

Before this PR, a release was always the next 0.x minor. After it, the same merge-the-release-PR flow ships 8.0.0-rc.1, 8.0.0-rc.2, … — still under dist-tag latest, with the GitHub Release marked pre-release.

Decision

This PR moves the publish pipeline onto the v8 release-candidate line:

1. Releases version as 8.0.0-rc.N — the counter advances on every release publish. "The v8 RC" is the product name; the number iterates freely underneath, so respins are cheap and there is no promise the final RC is literally rc.1.
2. latest keeps tracking the newest release, RC included. The package names this repo publishes (@prisma/orm-*, the platform packages, the prisma-next shim) have no pre-v8 stable audience to protect — a bare install is an early-access install. The frozen-latest concern belongs to the bare prisma package, which this repo does not publish — its v8 bin shim lives in prisma/prisma-cli, which publishes under next while v7 keeps latest.
3. pnpm bump-minor becomes pnpm bump-version, encoding the release policy: RC base → next RC; pre-8 stable base → 8.0.0-rc.1 (the one-time line transition); stable ≥ 8 → next minor.
4. RC releases keep the full release ceremony: committed release notes are required, and the GitHub Release is created with --prerelease whenever the version is on the RC line.

The root version deliberately stays 0.17.0 in this PR. Until the transition release PR lands, the pipeline behaves exactly as before (verified by running the publish paths locally — see Testing performed).

Notes for the reviewer

• No existing user is affected. latest semantics are unchanged (newest release); lockfiles pin resolved versions, and existing ^0.x ranges can never resolve to 8.0.0-rc.N (pre-releases don't satisfy stable ranges), so npm update never moves anyone onto the RC line — only fresh installs get RCs once the transition PR lands.
• The canonical root-version shape widens from "clean X.Y.Z only" to "clean X.Y.Z or X.Y.Z-rc.N" (assertCanonicalBase); anything else is still refused on main.
• check-upgrade-coverage's publish baseline changed from "last stable tag" to "last release tag" (v*-rc.N now counts; only -dev.*/-beta.* are excluded). Without this, every RC publish would diff against v0.17.0 forever and the coverage diff would grow without bound. The parseVersion/transitionLabel machinery needed no changes — it already discards pre-release suffixes, so RC respins land in PR-mode steady-state semantics (in-flight directory 8.0-to-8.1).
• composeDevVersion moved out of determine-version.ts into the pure utils module so the dev-counter logic (including the new RC-base handling and counter reset across base changes) is unit-tested rather than only exercised in CI. Dev builds on the RC line are 8.0.0-rc.X-dev.N.
• The skill/docs sweep (publish-npm-version, draft-release-notes, record-upgrade-instructions, extension-upgrade skill, docs/oss/versioning.md) renames bump-minor → bump-version and updates the release procedures for the RC line. draft-release-notes' range lower bound now explicitly treats -rc.N tags as releases, so an RC respin's notes cover exactly what changed since the previous RC.

How it fits together

1. The version-shape vocabulary (scripts/determine-version-utils.ts): assertCanonicalBase admits the two release shapes; computeNextReleaseVersion and composeDevVersion are pure helpers over them.
2. The publish decision (scripts/determine-version.ts): unchanged trigger model — a release bump publishes <base> under latest, routine pushes compose <base>-dev.N via the shared helper.
3. The maintainer entry point (scripts/bump-version.ts, pnpm bump-version): same idempotent read-from-HEAD design as before, now advancing to the next release version rather than the next minor.
4. The workflow ceremony (.github/workflows/publish.yml): the GitHub Release step adds --prerelease when the published version matches *-rc.*; everything else (notes check, lightweight dev tags) keeps its latest-scoped conditions.
5. The release-cycle baselines (scripts/check-upgrade-coverage.mjs, skills-contrib/draft-release-notes/SKILL.md): "previous release" means the previous release tag — stable or RC — so upgrade-coverage diffs and release notes span exactly one release cycle on the RC line too.
6. The policy documentation (docs/oss/versioning.md): a new "The v8 RC line" section states the scheme, why latest tracks RCs for these packages, where the bare-prisma next-channel policy lives, and the one-time transition; the procedures are updated to match.

Behavior changes & evidence

• A release bump whose root version is 8.0.0-rc.N publishes under latest with a pre-release GitHub Release; a stable bump behaves exactly as today. Implementation: scripts/determine-version.ts, .github/workflows/publish.yml. Evidence: computeNextReleaseVersion and assertCanonicalBase suites in scripts/determine-version-utils.test.ts.
• Dev builds on the RC line version as 8.0.0-rc.X-dev.N, with the counter resetting whenever the base moves (new RC counter, stable→RC transition). Implementation: composeDevVersion in scripts/determine-version-utils.ts. Evidence: the composeDevVersion suite in scripts/determine-version-utils.test.ts.
• pnpm bump-version from 0.17.0 produces 8.0.0-rc.1; from 8.0.0-rc.1 produces 8.0.0-rc.2; from a stable ≥ 8 produces the next minor. Implementation: scripts/bump-version.ts. Evidence: the computeNextReleaseVersion suite in scripts/determine-version-utils.test.ts.
• The publish-mode upgrade-coverage baseline resolves to the most recent release tag, including v*-rc.N. Implementation: scripts/check-upgrade-coverage.mjs.

Summary

Enables shipping the v8 RC early and iterating on it with frequent releases, using the exact publish flow that exists today — only the version shape and the pre-release marking change.

Testing performed

• pnpm test:scripts — 365 tests, 0 failures (includes the suites covering the new/changed version helpers).
• pnpm lint (full repo), pnpm lint:workflows, node scripts/validate-skills.mjs — all green.
• Local smoke-test of determine-version.ts against the real registry: dispatch resolves 0.17.0 → latest; push with unchanged version resolves 0.17.0-dev.N → dev (continuing from the registry's actual counter).
• .github/workflows/publish.yml parsed with the workspace yaml package to confirm validity after the edits.

Skill update

Updated in this PR: skills-contrib/publish-npm-version (RC-aware bump flow), skills-contrib/draft-release-notes (release-tag range bounds), skills-contrib/record-upgrade-instructions and skills/extension-author/prisma-8-extension-upgrade (bump-version rename). No end-user-facing CLI/API surface changes — the pipeline changes are maintainer-facing.

Alternatives considered

• Publishing RCs under a next dist-tag and freezing latest at 0.17.0 — rejected for these packages. Freezing latest protects a stable audience these package names don't have, npm publishes exactly one tag per publish so a second tag would need npm dist-tag add (which can't authenticate under OIDC trusted publishing — no long-lived token exists in this repo by design), and semver ranges already prevent any existing install from being moved onto an RC. The next channel remains the right design for the bare prisma package, whose latest genuinely must stay on v7; its v8 shim ships from prisma/prisma-cli.
• Nested pre-release identifiers (8.0.0-rc.1.1) for respins of a named RC — rejected. Semver orders them correctly but no major ecosystem package does this (Drizzle, React, and TypeScript all use a flat counter), and the flat rc.N counter makes ordering and automation trivial.
• Keeping bump-minor and adding a separate RC bump script — rejected; there is exactly one "advance to the next release version" operation and its meaning depends only on the current base's shape, so one script encoding the policy beats two scripts and a decision the maintainer must make each time.
• Bumping to 8.0.0-rc.1 in this same PR — rejected to preserve the one-PR-per-release convention: merging a release bump is the publish trigger, and that merge should be its own reviewable event with its own release notes.

Checklist

• All commits are signed off (git commit -s) per the DCO. The DCO status check will block merge if any commit is missing a Signed-off-by: trailer.
• I read CONTRIBUTING.md and the change is scoped to one logical concern.
• Tests are updated (or n/a if the change is doc-only / refactor with no behavioural delta).
• The PR title is in TML-NNNN: <sentence-case title> form (Linear ticket prefix + concise title naming the concrete deliverable). See .claude/skills/create-pr/SKILL.md for the full convention.
• The Skill update section above is filled in (or stated n/a — internal only).

Summary by CodeRabbit

• New Features

  • Added support for incremental release-candidate versions, including progression to the 8.0.0 release line.
  • Added development-version handling with consistent counter continuation and resets.
  • RC releases now use the latest channel and generate pre-release GitHub Releases.

• Documentation

  • Updated versioning, publishing, release-note, and upgrade guidance for RC and stable releases.
  • Replaced the minor-bump workflow with the pnpm bump-version command.
  • Clarified tag, channel, and release-note requirements across publishing workflows.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

The release process now supports 8.0.0-rc.N progression, shared development-version composition, RC publishing under latest, pre-release GitHub Releases, RC-aware validation, and updated versioning guidance. The bump-minor command is replaced by pnpm bump-version.

Changes

RC release flow

Layer / File(s)	Summary
Version progression and validation scripts/determine-version-utils.ts, scripts/determine-version-utils.test.ts	Release utilities now advance RC versions, transition pre-8 versions to 8.0.0-rc.1, advance stable 8.x minors, compose development versions, and validate RC bases.
Version resolution and bump command package.json, scripts/bump-version.ts, scripts/determine-version.ts, scripts/lint-throws.test.mjs	The package script and version-resolution paths now use pnpm bump-version, computeNextReleaseVersion, and shared development-version composition.
RC publish and release validation .github/workflows/publish.yml, scripts/check-release-notes.mjs, scripts/check-upgrade-coverage.mjs	RC versions publish under latest, create pre-release GitHub Releases, and remain eligible for release-tag coverage and release-note checks.
Release policy and contributor guidance docs/oss/versioning.md, skills-contrib/*, skills/prisma-8-extension-upgrade/SKILL.md	Documentation and skills describe the v8 RC cadence, RC release notes, latest behavior, and the pnpm bump-version procedure.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Sequence Diagram(s)

sequenceDiagram
  participant PublishWorkflow
  participant DetermineVersion
  participant CheckReleaseNotes
  participant GitHubRelease
  PublishWorkflow->>DetermineVersion: resolve RC or stable version
  DetermineVersion-->>PublishWorkflow: return version and latest tag
  PublishWorkflow->>CheckReleaseNotes: validate release notes
  CheckReleaseNotes-->>PublishWorkflow: return validation result
  PublishWorkflow->>GitHubRelease: create release with prerelease flag for RC

Loading

Possibly related PRs

• prisma/prisma#29883: Both PRs modify development-version resolution in scripts/determine-version.ts.

Suggested reviewers: aqrln

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 57.14% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: publishing 8.0.0 release candidates with the latest dist-tag tracking the RC line.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch tml-3170-rc-line-versioning

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/publish.yml:
- Around line 169-180: Move the Check release notes step before both
package-publication steps in the workflow, preserving its existing blessed-tag
and dry-run conditions and command. In .github/workflows/publish.yml lines
169-180, reorder the steps so the gate runs before publishing; in
docs/oss/versioning.md lines 70-73, retain the existing guarantee with no direct
change required.

In `@skills-contrib/publish-npm-version/SKILL.md`:
- Around line 47-56: Update the release-note guidance to consistently use the
previous blessed tag for RC releases: revise the remaining previous-stable-tag
references in skills-contrib/publish-npm-version/SKILL.md lines 41 and 93, and
change the graceful-degradation wording in
skills-contrib/draft-release-notes/SKILL.md lines 232-233 to reference the
previous blessed tag; keep the related instructions and links current.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: 9fa24af7-6891-493c-9cb6-e6f0914305d9

📥 Commits

Reviewing files that changed from the base of the PR and between 6cc73aa and b6ab8a6.

📒 Files selected for processing (14)

• .github/workflows/publish.yml
• docs/oss/versioning.md
• package.json
• scripts/bump-version.ts
• scripts/check-release-notes.mjs
• scripts/check-upgrade-coverage.mjs
• scripts/determine-version-utils.test.ts
• scripts/determine-version-utils.ts
• scripts/determine-version.ts
• scripts/lint-throws.test.mjs
• skills-contrib/draft-release-notes/SKILL.md
• skills-contrib/publish-npm-version/SKILL.md
• skills-contrib/record-upgrade-instructions/SKILL.md
• skills/extension-author/prisma-8-extension-upgrade/SKILL.md

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

[github-actions]

size-limit report 📦

Path	Size
postgres / no-emit	166.75 KB (0%)
postgres / emit	145.52 KB (0%)
mongo / no-emit	100.4 KB (0%)
mongo / emit	90.24 KB (0%)
cf-worker / no-emit	191.31 KB (0%)
cf-worker / emit	167.79 KB (0%)

[pkg-pr-new]

Open in StackBlitz

prisma-next

npm i https://pkg.pr.new/prisma-next@29899

@prisma/orm-extension-arktype-json

npm i https://pkg.pr.new/@prisma/orm-extension-arktype-json@29899

@prisma/orm-extension-middleware-cache

npm i https://pkg.pr.new/@prisma/orm-extension-middleware-cache@29899

@prisma/orm-extension-paradedb

npm i https://pkg.pr.new/@prisma/orm-extension-paradedb@29899

@prisma/orm-extension-pgvector

npm i https://pkg.pr.new/@prisma/orm-extension-pgvector@29899

@prisma/orm-extension-postgis

npm i https://pkg.pr.new/@prisma/orm-extension-postgis@29899

@prisma/orm-extension-supabase

npm i https://pkg.pr.new/@prisma/orm-extension-supabase@29899

@prisma/orm-family-mongo

npm i https://pkg.pr.new/@prisma/orm-family-mongo@29899

@prisma/orm-family-sql

npm i https://pkg.pr.new/@prisma/orm-family-sql@29899

@prisma/orm-framework

npm i https://pkg.pr.new/@prisma/orm-framework@29899

@prisma/orm-mongo

npm i https://pkg.pr.new/@prisma/orm-mongo@29899

@prisma/orm-postgres

npm i https://pkg.pr.new/@prisma/orm-postgres@29899

@prisma/orm-sqlite

npm i https://pkg.pr.new/@prisma/orm-sqlite@29899

@prisma/orm-target-mongo

npm i https://pkg.pr.new/@prisma/orm-target-mongo@29899

@prisma/orm-target-postgres

npm i https://pkg.pr.new/@prisma/orm-target-postgres@29899

@prisma/orm-target-sqlite

npm i https://pkg.pr.new/@prisma/orm-target-sqlite@29899

@prisma/orm-toolchain

npm i https://pkg.pr.new/@prisma/orm-toolchain@29899

commit: 9285e4a

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@skills-contrib/publish-npm-version/SKILL.md`:
- Around line 47-56: Update the “Fetch and determine the target version”
instructions so computeNextReleaseVersion is loaded from the fetched origin/main
revision rather than the potentially dirty current worktree. Ensure the
branch/PR NEXT value and the authoritative pnpm bump-version calculation use the
same origin/main helper and produce an identical version.
- Line 114: Correct the idempotency statement in the skill documentation:
clarify that only pnpm bump-version is idempotent, while rerunning the full
skill fails when the release branch or sibling worktree created by git worktree
add already exists. Document how to reuse or remove the existing worktree, or
update Step 2 to reuse it before describing rerun behavior.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: d501530a-3980-44e7-8504-3aad818b074e

📥 Commits

Reviewing files that changed from the base of the PR and between 6cc73aa and 7128beb.

📒 Files selected for processing (14)

• .github/workflows/publish.yml
• docs/oss/versioning.md
• package.json
• scripts/bump-version.ts
• scripts/check-release-notes.mjs
• scripts/check-upgrade-coverage.mjs
• scripts/determine-version-utils.test.ts
• scripts/determine-version-utils.ts
• scripts/determine-version.ts
• scripts/lint-throws.test.mjs
• skills-contrib/draft-release-notes/SKILL.md
• skills-contrib/publish-npm-version/SKILL.md
• skills-contrib/record-upgrade-instructions/SKILL.md
• skills/prisma-8-extension-upgrade/SKILL.md

🚧 Files skipped from review as they are similar to previous changes (9)

• scripts/lint-throws.test.mjs
• scripts/check-release-notes.mjs
• package.json
• skills-contrib/draft-release-notes/SKILL.md
• scripts/determine-version-utils.test.ts
• .github/workflows/publish.yml
• skills-contrib/record-upgrade-instructions/SKILL.md
• scripts/check-upgrade-coverage.mjs
• scripts/determine-version.ts

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@scripts/determine-version-utils.ts`:
- Around line 7-8: Restrict RC_BASE_PATTERN to match only the supported 8.0.0 RC
line with rc numbers starting at 1, and ensure assertCanonicalBase() rejects
other RC bases such as 0.17.0-rc.0, 8.0.1-rc.1, and 9.2.3-rc.1. Add negative
tests covering non-8.0.0 RC bases and rc.0 while preserving valid RC behavior.

In `@scripts/determine-version.ts`:
- Around line 131-134: Route RC release results to next and stable release
results to latest in scripts/determine-version.ts (131-134). Update
.github/workflows/publish.yml (10-16, 145-155, 169-180, 182-216) to document
both channels, exclude both release tags from lightweight tags, gate release
notes for both, and create the appropriate RC or stable GitHub Release. Update
scripts/check-release-notes.mjs (4-7, 34-35, 182) so checks apply to every
release and error text names next and latest. Update docs/oss/versioning.md
(34-45, 69-85) to document next for RCs, stable latest, and both workflow/manual
procedures.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: bc007d36-4d43-4134-8204-085b10d12663

📥 Commits

Reviewing files that changed from the base of the PR and between 6cc73aa and 38e1d59.

📒 Files selected for processing (14)

• .github/workflows/publish.yml
• docs/oss/versioning.md
• package.json
• scripts/bump-version.ts
• scripts/check-release-notes.mjs
• scripts/check-upgrade-coverage.mjs
• scripts/determine-version-utils.test.ts
• scripts/determine-version-utils.ts
• scripts/determine-version.ts
• scripts/lint-throws.test.mjs
• skills-contrib/draft-release-notes/SKILL.md
• skills-contrib/publish-npm-version/SKILL.md
• skills-contrib/record-upgrade-instructions/SKILL.md
• skills/prisma-8-extension-upgrade/SKILL.md

🚧 Files skipped from review as they are similar to previous changes (9)

• package.json
• skills-contrib/record-upgrade-instructions/SKILL.md
• scripts/lint-throws.test.mjs
• scripts/check-upgrade-coverage.mjs
• skills-contrib/draft-release-notes/SKILL.md
• skills/prisma-8-extension-upgrade/SKILL.md
• scripts/determine-version-utils.test.ts
• scripts/bump-version.ts
• skills-contrib/publish-npm-version/SKILL.md

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

docs/oss/versioning.md (2)

71-71: 🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

Qualify the latest claim for prisma.

The prisma package publishes RC versions under next until 8.0.0 final. This sentence says that the release publishes the new version under latest without stating the exception. Clarify that latest applies to the other packages and next applies to prisma.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/oss/versioning.md` at line 71, Update the versioning documentation
sentence describing the publish dist-tag so it qualifies the claim: use `next`
for RC versions of the `prisma` package until `8.0.0` final, while `latest`
applies to the other packages. Preserve the existing release-trigger and
pre-release behavior details.

---

7-8: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Update the remaining 0.x release examples.

The new note changes the release line to 8.0.0-rc.N, but this section still describes regular 0.x minors, including 0.8.1 patch releases and “each minor.” Rewrite these examples for RC respins, or clearly label the 0.x text as historical transition guidance.

As per coding guidelines, documentation must remain current.

Proposed documentation update

-## Pre-1.0: deliberately unstable
+## Early access: deliberately unstable

-**Breaking changes ship in regular minor bumps.**
+**Breaking changes may ship in any RC respin before `8.0.0` final.**

-**Releases are frequent.** The cadence is "ship a minor whenever the next batch of work is cohesive enough to warrant one"
+**Releases are frequent.** The cadence is "ship the next RC whenever the next batch of work is cohesive enough to warrant one"

-**There are no patch releases of older minors.**
+**On the RC line, fixes ship as the next `rc.N`, not as patch releases.**

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/oss/versioning.md` around lines 7 - 8, Update the release examples in
the versioning guidance to use the current 8.0.0-rc.N RC respin model instead of
presenting 0.x minors and 0.8.1 patches as current behavior. If retaining the
0.x examples, explicitly label them as historical transition guidance and
preserve the updated v8 RC policy.

Source: Coding guidelines

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@scripts/publish-packages-utils.mjs`:
- Around line 64-71: Update the release-tag documentation to match
planPackagePublish: in scripts/publish-packages-utils.mjs lines 64-71, state
that Prisma 7 retains latest while Prisma 8 releases use next; apply the same
policy in scripts/publish-packages.mjs lines 16-20; and revise
packages/9-public/prisma/README.md lines 3-5 to remove the 8.0.0-final
transition promise and document the supported Prisma 8 installation channel.

---

Outside diff comments:
In `@docs/oss/versioning.md`:
- Line 71: Update the versioning documentation sentence describing the publish
dist-tag so it qualifies the claim: use `next` for RC versions of the `prisma`
package until `8.0.0` final, while `latest` applies to the other packages.
Preserve the existing release-trigger and pre-release behavior details.
- Around line 7-8: Update the release examples in the versioning guidance to use
the current 8.0.0-rc.N RC respin model instead of presenting 0.x minors and
0.8.1 patches as current behavior. If retaining the 0.x examples, explicitly
label them as historical transition guidance and preserve the updated v8 RC
policy.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: 90dedd14-7a97-4877-9f4b-9ad093200bf2

📥 Commits

Reviewing files that changed from the base of the PR and between 38e1d59 and 9413481.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (9)

• docs/oss/versioning.md
• packages/9-public/prisma/README.md
• packages/9-public/prisma/bin/prisma-next.mjs
• packages/9-public/prisma/package.json
• packages/9-public/prisma/scripts/lint-sync.mjs
• scripts/determine-version.ts
• scripts/publish-packages-utils.mjs
• scripts/publish-packages-utils.test.mjs
• scripts/publish-packages.mjs

🚧 Files skipped from review as they are similar to previous changes (1)

• scripts/determine-version.ts

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/oss/versioning.md`:
- Line 34: Update the package and dist-tag policy in the versioning
documentation to explicitly state that the bare prisma package is published
under next before v8, while published packages otherwise use latest. Remove or
revise adjacent statements claiming this repository does not publish prisma or
that v8 publishing belongs exclusively to prisma/prisma-cli, keeping the post-v8
contract accurate.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: 081b9149-5b4d-4666-b145-84e646727f5f

📥 Commits

Reviewing files that changed from the base of the PR and between 0146c58 and 9285e4a.

📒 Files selected for processing (14)

• .github/workflows/publish.yml
• docs/oss/versioning.md
• package.json
• scripts/bump-version.ts
• scripts/check-release-notes.mjs
• scripts/check-upgrade-coverage.mjs
• scripts/determine-version-utils.test.ts
• scripts/determine-version-utils.ts
• scripts/determine-version.ts
• scripts/lint-throws.test.mjs
• skills-contrib/draft-release-notes/SKILL.md
• skills-contrib/publish-npm-version/SKILL.md
• skills-contrib/record-upgrade-instructions/SKILL.md
• skills/prisma-8-extension-upgrade/SKILL.md

🚧 Files skipped from review as they are similar to previous changes (12)

• skills-contrib/record-upgrade-instructions/SKILL.md
• package.json
• scripts/lint-throws.test.mjs
• .github/workflows/publish.yml
• scripts/determine-version.ts
• scripts/check-upgrade-coverage.mjs
• skills-contrib/publish-npm-version/SKILL.md
• scripts/determine-version-utils.test.ts
• scripts/check-release-notes.mjs
• skills-contrib/draft-release-notes/SKILL.md
• scripts/bump-version.ts
• skills/prisma-8-extension-upgrade/SKILL.md