docs(site): add changelog entry 2026-07-24

[ankur-arch]

What

Adds the weekly changelog entry for 2026-07-24, covering everything merged 2026-07-17 → 2026-07-24 across the 15 loggy-core repos (Loggy's extraction scope), minus what the 2026-07-17 entry already published.

Highlights

1. Object Store buckets — S3-compatible storage as a project resource (Console + /v1/buckets Management API + MCP tools). Vendor name stripped per the release-notes-writer rubric.
2. Console workspace overview — the new /dashboard overview (usage, invoice, deploy health, top projects); usage details moved to /usage.
3. Prisma Next 0.16.0 — sourced from the committed docs/releases/v0.16.0.md; breaking changes condensed into a callout with the 0.15-to-0.16 upgrade recipe link.

Also: Compute SDK detectComputeApp (0.37.0), repo-picker pagination, truthful pre-deploy endpoint domains, Postgres cold-start resilience, agent-ready docs, Plasmic guide, Breaking callout for the removed /v1/compute-services + /v1/versions endpoints, and three new blog posts under Guides.

Held out (flagged, for reviewer awareness)

• Prisma Studio Jul 18 batch (Update 037-relation-queries.mdx #1486, Update $disconnect remark #1544–Testing repel out for interactive playground #1555: row-count footer, PG type aliases, persisted visualizer layout, 10 fixes): merged but @prisma/studio-core latest on npm is still 0.33.0, so nothing shipped carries them. They headline next week's entry once the next Studio release ships. If a release lands before this merges, promote them into this entry.
• GitHub import flow + click-to-deploy templates: gated behind an experimental flag / mid-rollout → excluded.
• Prisma Next PRs merged after the 0.16.0 bump (error-code consolidation, name-identified indexes, config renames): unreleased → next entry.
• Full per-PR decision log (published / flagged / excluded with reasons) and the Slack changelog.summary.json are in the session scratchpad; ping me if you want them attached.

Review checklist

• Object Store: confirm Console shows no Early Access banner (entry uses plain "New" with narrow claims).
• Workspace overview merged today — confirm it's deployed to production Console before merging.
• No internal codenames, Linear IDs, or private links; no em dashes; all PR links public-repo only.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • Added Object Store buckets for file storage with Prisma Postgres and Prisma Compute.
  • Updated Prisma Console with an overview dashboard and dedicated Usage page.
  • Improved Prisma Next contracts, temporal presets, diagnostics, and relation handling.
  • Enhanced Compute SDK workflows, repository pagination, and account switching.
  • Added agent-ready Prisma documentation and a Plasmic integration guide.
• Bug Fixes
  • Improved database wake-up reliability and pre-deployment endpoint domains.
  • Fixed Prisma Next decoding, migration ordering, SQL correctness, and contract inference.
• Breaking Changes
  • Prisma Next 0.16.0 requires re-running contract emit.
  • Deprecated Management API endpoints were removed.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Jul 24, 2026 3:02pm
docs	Ready	Preview, Comment	Jul 24, 2026 3:02pm
eclipse	Ready	Preview, Comment	Jul 24, 2026 3:02pm
site	Ready	Preview, Comment	Jul 24, 2026 3:02pm

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 19 seconds

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: a4021ff2-c2f7-42e3-a6b3-33d72f1e3cdb

📥 Commits

Reviewing files that changed from the base of the PR and between bd56683 and 14d1e23.

📒 Files selected for processing (1)

• apps/site/content/changelog/2026-07-24.mdx

Walkthrough

The PR adds the July 24, 2026 changelog entry, covering Object Store buckets, Console dashboard changes, Prisma Next 0.16.0, Compute and Postgres updates, agent-ready documentation, breaking changes, related articles, and support resources.

Changes

Product changelog

Layer / File(s)	Summary
Entry metadata and highlights apps/site/content/changelog/2026-07-24.mdx	Adds changelog metadata and highlights for Object Store, the Console workspace dashboard, Prisma Next 0.16.0, and agent-ready documentation.
Product updates and fixes apps/site/content/changelog/2026-07-24.mdx	Lists Prisma Next fixes, Compute updates, Postgres cold-start provisioning changes, and Prisma documentation additions.
Breaking changes and resources apps/site/content/changelog/2026-07-24.mdx	Documents contract emission changes, removed Management API endpoints, migration guidance, related articles, and support information.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding the 2026-07-24 site changelog entry.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/changelog-2026-07-24

---

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

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	Jul 24, 2026, 3:29 PM