docs(docs): label the Accelerate URL forms correctly in the Console retirement warning - #8226
Conversation
…etirement warning The warning called `prisma://accelerate.prisma-data.net/?api_key=...` a hosted Accelerate connection for Prisma Postgres. That form belongs to standalone Accelerate environments (the Step 4 resource); hosted Prisma Postgres uses `prisma+postgres://accelerate.prisma-data.net/?api_key=...`, as documented in postgres/database/switch-from-accelerate. Name both forms so a reader can tell which retirement path applies. Refs: #8218
🍈 Lychee Link Check Report8 links: ✅ All links are working!Full Statistics Table
|
|
Review clean at 32fc0ca What it does. One prose line in What I checked.
Risk: low. A single-sentence prose correction to a page that already carried the warning; it changes no links, code, structure, or navigation, and it makes the warning match the two pages it points at. Follow-ups. The PR body already proposes the Step 4 "For Accelerate" retirement-notice gap as a task, so I did not re-propose it. The stale — reviewer |
1 participant
Overview
This lands the one-line fix from #8220's round-2 review, which was pushed to that PR's branch (
ecc2c30bbe563f44aba3bd129dab75d9e0b6bd76) three minutes after the PR was merged at its round-1 head. The commit is cherry-picked onto currentmainunchanged.What it delivers
console/getting-started.mdx, the:::warning[Accelerate retirement]block in Step 6, calledprisma://accelerate.prisma-data.net/?api_key=…a "hosted Accelerate connection for Prisma Postgres". That is the wrong product:prisma://accelerate.prisma-data.net/?api_key=…is the standalone Accelerate environment form — seeaccelerate/getting-started.mdx(line 47), and it is what the "For Accelerate" resource in Step 4 of this same page creates.prisma+postgres://accelerate.prisma-data.net/?api_key=…is the hosted Prisma Postgres form — seepostgres/database/switch-from-accelerate.mdx(lines 9 and 24).The warning links to two different migration paths, so a reader matching their own connection string against the label was being pointed at the wrong one. The sentence now names both forms and ties each to its product. Nothing else changed; the diff is one line.
How I tested it
From
apps/docs, on this branch (branched frommainata687e6f, no merge needed):pnpm lint:links— 687 files, 0 errorspnpm lint:spellcheck— 826 files, 0 issuespnpm test:llm-markdown— 9/9 snapshots passpnpm lint:images— cleanpnpm lint:agent-ready— 0 failures, 0 warningspnpm test— 7/7 passpnpm lint:code— 6307 total, byte-identical to the baseline withmain's version of the file restored; the page's single pre-existing "missing title" warning is unchangedI also re-derived the finding from the source pages rather than trusting the review comment, which is where the
accelerate/getting-started.mdxandswitch-from-accelerate.mdxline references above come from.Assumptions and decisions
ecc2c30brather than rewriting the sentence, since that commit was already reviewed in docs(docs): replace hosted Accelerate connections in the Netlify, viewing-data and Console guides #8220's round-2 read and its wording is accurate. The original author and commit message (including itsRefs: prisma/web#8218) are preserved.types:checkorbuildrun: this is a prose-only change to one MDX file with no code, perapps/docs/CLAUDE.md, which scopes those two to code changes.Follow-ups noticed, left alone
img/ppg-tableplus.png,ppg-datagrip.png,ppg-dbeaver.pngandppg-postico.pngscreenshots inguides/postgres/viewing-data.mdxstill show127.0.0.1tunnel connections, while the surrounding text (rewritten in docs(docs): replace hosted Accelerate connections in the Netlify, viewing-data and Console guides #8220) now describes a directdb.prisma.io:5432connection. Left as a note rather than a task: it needs someone to take new screenshots, not a code change.@prisma/configvsprisma/configimport inconsistency that docs(docs): replace hosted Accelerate connections in the Netlify, viewing-data and Console guides #8220 flagged is already resolved —grepfinds nofrom "@prisma/config"left incontent/docs/, so docs(guides): import defineConfig from prisma/config in the Vercel Postgres guide #8222 closed it out.