Repository navigation
fix(cli): agent hints run @prisma/cli@latest, not the stale next tag - #346
Open
gregory-boch-prisma wants to merge 1 commit into
Open
gregory-boch-prisma wants to merge 1 commit into
gregory-boch-prisma wants to merge 1 commit into
Conversation
The post-login skills tip and the PROJECT.DELETE_BLOCKED next action print `npx -y @prisma/cli@next ...`. Since the 2026-08-25 cutover the RC line publishes on `latest` and the publish path no longer moves `next` (docs/oss/versioning.md), so those hints install an older RC. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedEnable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Next included review available in 36 minutes. View limit details
Comment |
commit: |
gregory-boch-prisma
added a commit
that referenced
this pull request
Oct 14, 2026
## What The READMEs that models and people read first (the repo README and the npm READMEs for `prisma` and `@prisma/cli`), the hello-world example README and the glossary still describe the state before the 2026-08-25 cutover. This PR brings them in line with `docs/oss/versioning.md`. Text only, no code. ## Changes and sources | File | Was | Now | Source | | --- | --- | --- | --- | | `packages/prisma/README.md`, `packages/cli/README.md`, `README.md`, `examples/hello-world/README.md` | `npm install --save-dev prisma@next`, `pnpm add -D prisma@next`, `@prisma/cli@next` | plain `prisma` / `@prisma/cli` | `docs/oss/versioning.md`, Dist-tag convention: "`next` — kept alive but no longer moved by the publish path (operator ruling 2026-08-25) ... New text should say plain `prisma`." | | the repo README and both npm READMEs | "The 8.0.0 release candidates publish as `prisma` on the `next` dist-tag." | "... on the `latest` dist-tag." | `docs/oss/versioning.md`: "every release publishes under `latest`, RC-line versions included (operator cutover ruling 2026-08-25 ...)". The root README's own Publishing section already says `latest`. | | `docs/reference/glossary.md`, "Beta package" row | "the RC line publishes on the `next` dist-tag" | "... on the `latest` dist-tag", versioning link kept | same as above | | the repo README and both npm READMEs | "public beta", "Beta of the unified Prisma CLI", "Install the beta package", "Beta notes" | "release candidate", "Install the package", "Release candidate notes" | `docs/oss/versioning.md`: "Prisma 8 ships as a release-candidate line ahead of `8.0.0` final". The npm READMEs already say "This is a release-candidate package" two lines below the old heading. | | `README.md`, Command Model | groups `database` and `app` | `postgres` and `service` | `packages/cli/src/commands/` has `auth`, `branch`, `bucket`, `git`, `postgres`, `project`, `service`. The npm README's command table lists the same groups. | After this PR, `git grep -nE "prisma@next|@prisma/cli@next|on the .next. dist-tag|public beta" -- README.md 'packages/*/README.md' examples docs/reference` returns nothing. ## Why it matters `npm view prisma dist-tags` and `npm view @prisma/cli dist-tags` on 2026-10-12: ``` next: 8.0.0-rc.10 (published 2026-08-25) latest: 8.0.0-rc.22 (published 2026-10-08) ``` So the documented install command gives a reader a build that is twelve release candidates old. The npm README is also what AI assistants read when they describe the Prisma CLI, and "public beta" is the wording they repeat. ## Related - #346 changes `PRISMA_CLI_PACKAGE_SPEC` in `packages/cli/src/cli-command.ts` to `@prisma/cli@latest`, with a unit test. That is the code change CodeRabbit asked for here; it is a separate PR so this one stays text-only. ## Not in this PR - Whether to re-point the `next` dist-tag at the current release. #346 lists the three `npm dist-tag add` commands for the release operator. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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.
What
PRISMA_CLI_PACKAGE_SPECinpackages/cli/src/cli-command.tswas@prisma/cli@next. Two hints print it throughformatPrismaCliCommand:commands/auth/agent-setup-tip.ts, viaresolvePrismaCliPackageCommand):npx -y @prisma/cli@next skills syncPROJECT.DELETE_BLOCKEDnext action (lib/project/provider.ts):npx -y @prisma/cli@next service delete --service <name>Since the 2026-08-25 cutover the RC line publishes on
latest, and the publish path no longer movesnext(docs/oss/versioning.md). So both hints install an older RC. This PR sets the spec to@prisma/cli@latestand rewrites the comment above it, which still described the pre-cutover state.This is the code half of the CodeRabbit comment on #331 (that PR stays text-only).
npm today (2026-10-12)
prismahas the same pair.@prisma/cli-enginehasnext0.6.1 andlatest0.7.0.Changes
packages/cli/src/cli-command.ts:${PRISMA_CLI_PACKAGE_NAME}@latest, and a comment that says why.packages/cli/tests/cli-command.test.ts(new):formatPrismaCliCommand(["skills", "sync"])returnsnpx -y @prisma/cli@latest skills sync; a detected runner keeps the spec (pnpm dlx @prisma/cli@latest ...); binary invocation staysprisma skills sync; thePROJECT.DELETE_BLOCKEDrun-command action uses@latest.No other test asserted the old spec (
git grep -nE "cli@next|PRISMA_CLI_PACKAGE_SPEC|formatPrismaCliCommand|resolvePrismaCliPackageCommand" packages).A bare
@prisma/cliwould also work if you prefer that. I followed CodeRabbit's suggestion on #331.Testing
On Node 24.21.0 and pnpm 11.6.0:
pnpm install --frozen-lockfilepnpm typecheck: 9 tasks passpnpm lint: 483 files, no findingspnpm --filter @prisma/cli test: 65 files, 1031 passed, 1 skippedFor the release operator (optional, not in this PR)
docs/oss/versioning.md:43says the operator pointsnextat the current release by hand. If you wantnextto stop lagging until it is retired:Drafted with Claude Code.
🤖 Generated with Claude Code