docs(site): add changelog entry 2026-07-17#8078
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughAdds the July 17, 2026 changelog entry with Prisma product highlights, detailed updates, fixes, guides, and an enterprise support callout. ChangesChangelog entry
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (3)
apps/site/content/changelog/2026-07-17.mdx (3)
75-75: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low valueUse "afterward" (American English) instead of "afterwards".
✍️ Suggested fix
- chosen once during project creation in the Prisma Console and immutable afterwards. + chosen once during project creation in the Prisma Console and immutable afterward.🤖 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 `@apps/site/content/changelog/2026-07-17.mdx` at line 75, Update the Prisma Compute changelog entry to use the American English term “afterward” instead of “afterwards,” without changing the rest of the documented behavior.Source: Linters/SAST tools
23-23: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low valueThree consecutive sentences begin with "Prisma" — consider rewording for variety.
The last three sentences of the overview all start with the product name. Leading one with the feature instead would improve readability.
✍️ Suggested reword
-Prisma Postgres warns you before you hit your database limit, with a dashboard banner and emails at 75% and at the limit. Prisma Studio adds a Migrations view that renders Prisma Next migration history as visual contract diffs. Prisma ORM extends its AI safety checkpoint to `prisma db push --accept-data-loss`. +Prisma Postgres warns you before you hit your database limit, with a dashboard banner and emails at 75% and at the limit. A new Migrations view in Prisma Studio renders Prisma Next migration history as visual contract diffs. The ORM's AI safety checkpoint now extends to `prisma db push --accept-data-loss`.🤖 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 `@apps/site/content/changelog/2026-07-17.mdx` at line 23, Reword the final three sentences in the changelog overview so they do not all begin with “Prisma.” Lead at least one sentence with its feature or behavior while preserving the existing details about database-limit warnings, the Migrations view, and the AI safety checkpoint.Source: Linters/SAST tools
1-18: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winConsider adding a
summaryfield to the frontmatter.The changelog listing page (
apps/site/src/app/changelog/page.tsx) derives each card's preview text fromentry.data.summary ?? entry.data.description ?? getReleaseNotePreview(...). Without asummary, the card will fall back to an auto-generated preview, which may not surface the most important updates. A curated one-liner would give you control over what appears on the/changeloglisting.As per the upstream contract defined in
apps/site/source.config.ts,summaryis an optionalz.string()field in thereleaseNotescollection schema.✨ Suggested addition
--- title: "Use Prisma Next with Supabase and pin Prisma Compute preview branches" date: "2026-07-17" version: "2026-07-17" slug: "2026-07-17" +summary: "Prisma Next runs Supabase projects end to end, Prisma Compute reclaims idle previews, Prisma Postgres warns before database limits, and Prisma Studio adds a Migrations view." headline: "Use Prisma Next with Supabase and pin Prisma Compute preview branches"🤖 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 `@apps/site/content/changelog/2026-07-17.mdx` around lines 1 - 18, Add a curated one-line `summary` string to the release-note frontmatter block for this changelog entry, alongside the existing metadata fields. Keep it concise and focused on the entry’s primary updates so the changelog listing uses it instead of the generated preview.
🤖 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.
Nitpick comments:
In `@apps/site/content/changelog/2026-07-17.mdx`:
- Line 75: Update the Prisma Compute changelog entry to use the American English
term “afterward” instead of “afterwards,” without changing the rest of the
documented behavior.
- Line 23: Reword the final three sentences in the changelog overview so they do
not all begin with “Prisma.” Lead at least one sentence with its feature or
behavior while preserving the existing details about database-limit warnings,
the Migrations view, and the AI safety checkpoint.
- Around line 1-18: Add a curated one-line `summary` string to the release-note
frontmatter block for this changelog entry, alongside the existing metadata
fields. Keep it concise and focused on the entry’s primary updates so the
changelog listing uses it instead of the generated preview.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 00e82636-31cb-4668-a7ca-af667de58c68
📒 Files selected for processing (1)
apps/site/content/changelog/2026-07-17.mdx
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
External changelog for the 2026-07-10..2026-07-17 window, generated with content-write-changelog from Loggy-tracked merged PRs across the platform repos (prisma-next, studio, prisma, prisma-engines, web, and the private Console and data-plane repos). Linear: DR-7834 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ot to 2026-07-17 entry Adds the Studio Migrations view launch post and docs links plus the timeline screenshot to the Studio highlight, and the two new Postgres posts (pgvector, SKIP LOCKED) to guides. Linear: DR-7834 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ankur-arch
force-pushed
the
changelog/2026-07-17
branch
from
July 17, 2026 12:47
e0f05f4 to
2cd34f3
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 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 `@apps/site/content/changelog/2026-07-17.mdx`:
- Line 79: Update the Prisma Compute changelog entry to use the American-English
spelling “afterward” instead of “afterwards,” without changing the surrounding
behavior or details.
- Around line 29-36: Update the command block in the changelog entry to include
the final verification step, using `npx prisma-next db verify --db
"$DATABASE_URL"` after migration so it matches the documented
plan-to-migrate-to-verify flow.
- Around line 1-17: Add a summary or metaDescription frontmatter field to the
2026-07-17 changelog entry, using concise text that reflects the page’s opening
copy so generateMetadata produces entry-specific SEO and Open Graph metadata
instead of the generic fallback.
🪄 Autofix (Beta)
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: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 147b9616-845b-4479-beac-590dff889d0c
⛔ Files ignored due to path filters (1)
apps/site/public/changelog/studio-migrations-timeline.pngis excluded by!**/*.png
📒 Files selected for processing (1)
apps/site/content/changelog/2026-07-17.mdx
Adds metaDescription frontmatter so the entry gets its own SEO/OG text, completes the Supabase demo with the db verify step shown in prisma-next#997, and fixes an en-US spelling. Linear: DR-7834 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ankur-arch
force-pushed
the
changelog/2026-07-17
branch
from
July 17, 2026 13:32
c15fc21 to
59d6587
Compare
Linear: DR-7834
Linear: DR-7834 Co-Authored-By: Claude Fable 5 <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
Adds the external changelog entry for 2026-07-10..2026-07-17 at
apps/site/content/changelog/2026-07-17.mdx.Generated with
content-write-changelogfrom Loggy's tracked repos for the same window: merged PRs acrossprisma-next,studio,prisma,prisma-engines,web,project-compute, and the private Console and data-plane repos (pdp-control-plane,pdp-metal,pdp-cloudflare).prisma/prismais not Loggy-tagged but was swept manually, matching prior entries.Review focus
Triage notes
Included items that need reviewer confirmation
PREVIEW_ENV_RECLAIM_ENABLED(pdp-control-plane#4473). Treated as live because pdp-control-plane#4545 describes it as "the idle-preview reclaim that now auto-frees quota slots". Confirm the flag is on in production before merge. No public PR.findcases and giveupdatea headline #4507/chore(deps): bump @sideway/formula from 3.0.0 to 3.0.1 #4508/feat: Introduced additional flags for init #4509/docs: dotenv with jest script #4512/Fix 404 #4517 and project-compute#108. No public PR;us-east-1fallback and field namedefaultRegionare from the PR descriptions.Flagged (held out of the entry)
Excluded
map,onUpdateandonDeletearguments to schema reference #4399, add new generator: prisma-json-types-generator #4436, Fix/main #4462, The select dropdown menu for official site has overlapping issue #4471/Update 400-self-relations.mdx : Fix typo, by swapping follower and following relations #4472 (spec/schema for reclaim, covered by the shipped item), Test/gh action #4475/feat(views): PostgreSQL Introspection #4476/Updated Code for instantiating single PrismaClient instance #4478-Link to PCE blog post from the docs #4481, feat: update "binaryTargets" reference for Linux Alpine arm64 #4491/prisma studiodoes not actually supportdirectUrl#4492, feat: remove references to introspection-engine and PRISMA_INTROSPECTION_ENGINE #4495, docs: add jameszhang-a as a contributor for bug #4498/docs: fix reference to postgresql docs of 'create role' #4499, Update index.mdx #4501 (internal Turborepo remote-cache service), Clarifies inability to usedirectUrlwithprisma studio#4510/Running tests on different environments test script #4511, Blogging platform schema example #4514, remove duplicate words #4518, update: brand consistency for homepage #4526/retrigger ci by Lost Pixel #4527 (Console Studio 0.32.0 bump, superseded by the 0.33.0 CLI release), Update index.mdx #4531, test: Lost Pixel baselines #4533, Add example for raw query in client extensions #4545-adjacent chores, Missingawaitin Prisma's Sequelize comparison #4550-Clarify what are Checked and Unchecked Types and the difference between them. #4552, chore(deps): update react monorepo #4554/docs: Update Projects, Environments, and Schema Viewer docs with new Upload schema option #4556, Fix/custom 404 page #4559/Unit Testing guide's with-singleton.ts tests fail to run #4560/fix: unit test from Unit Testing guide failing to run #4561 (migration PR for held-out Object Store)): internal process, infra, or duplicates.typescript/rest-nextjsexample path #964/Updatetypescript/rest-nextjsexample path #965/Revise quickstart #967, Content re-org #971/Redirects #972, Support third-level navigation #976 (prerequisite of the published Janpio patch 1 #984 fix), Improve linking to pages moved to Reference #977-Search field issues #979, All sub-sections automatically expanded sometimes (left-hand nav) #988 (version bump), Review use of smooth scroll #989-Add documentation about 2 more available Studio arguments #994, 2.11.0 #996, Search: no result styling could be improved #1001): parser/differ/codec/LSP/ledger machinery, refactors, tests, project close-outs. MSSQL connection string link from main page #957/Find a new home for database management tools / db push conceptual #960/Top-level landing page summaries #985/Back to top on a per-section basis #987/Close search with ESC #990/Applying some post-redesign styling TLC #997 are represented by the Supabase highlight's citations.openssldependency bump with no advisory cited in the PR.ignite,drive,shared-agent-skills): internal documentation; no merged PRs returned in the window.Linear: DR-7834
🤖 Generated with Claude Code
Summary by CodeRabbit
prisma db push --accept-data-lossnow requires the same explicit confirmation as--force-reset.