docs(site): add changelog entry 2026-08-07 - #8136
Conversation
Covers merged PRs 2026-08-03 to 2026-08-07 across the loggy-core repos. Highlights: Prisma Compute one-click template deployment (now open to every workspace) and the /new/clone Deploy Button, and the first Prisma 8 release candidate installable as a single package. Includes a Console template-catalog screenshot served from public/changelog. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
WalkthroughAdds the August 7, 2026 changelog. It covers platform updates, Prisma 8 release changes, product fixes, security updates, billing changes, and an Alchemy deployment guide. ChangesAugust 7 changelog
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
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-08-07.mdx`:
- Around line 95-103: Add the JSON Content-Type header to the POST create-token
curl command, alongside its existing Authorization header, so the request body
is sent as application/json. Leave the revoke command unchanged.
- Around line 43-47: Remove the unsupported Prisma Deploy Button URL block from
the changelog entry, or replace it with a documented Prisma endpoint and valid
parameters. Do not retain the `console.prisma.io/new/clone` link or its
Vercel-style `repository-url` and `env` query parameters.
- Around line 51-62: Update the Prisma 8 release-candidate changelog entry to
explicitly instruct existing installations to remove all `@prisma-next/`*
dependencies and add `@prisma/orm-postgres` to package.json. Clarify that npm
update or reinstalling an unchanged manifest does not perform this package-name
migration.
🪄 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: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: de8a4fc6-e7c8-4c27-8ebe-a8571e774336
⛔ Files ignored due to path filters (1)
apps/site/public/changelog/prisma-compute-template-catalog.pngis excluded by!**/*.png
📒 Files selected for processing (1)
apps/site/content/changelog/2026-08-07.mdx
| ```text | ||
| https://console.prisma.io/new/clone | ||
| ?repository-url=https://github.com/<owner>/<repo> | ||
| &env=DATABASE_URL,WEBHOOK_SECRET | ||
| ``` |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Find the route implementation and all published examples.
rg -n -C 5 -g '*.{md,mdx,ts,tsx,js,jsx}' \
'console\.prisma\.io/new/clone|repository-url|new/clone|[?&]env=' appsRepository: prisma/web
Length of output: 1572
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '%s\n' '--- tracked files containing relevant terms ---'
rg -n -C 4 \
'console\.prisma\.io/new/clone|repository-url|new/clone|[?&]env=' \
-g '!apps/site/content/changelog/2026-08-07.mdx' .
printf '%s\n' '--- changelog context ---'
sed -n '34,50p' apps/site/content/changelog/2026-08-07.mdxRepository: prisma/web
Length of output: 196
🌐 Web query:
Prisma Deploy Button console.prisma.io/new/clone repository-url env
💡 Result:
There is no official "Prisma Deploy Button" console.prisma.io/new/clone URL structure [1][2][3][4]. The URL structure you mentioned—specifically console.prisma.io/new/clone with repository-url and env parameters—is characteristic of the Vercel Deploy Button, which uses exactly those query parameters (repository-url and env) to pre-configure project deployments [5][6][7]. Prisma documentation indicates that Prisma Compute and other managed services are primarily managed through the Prisma Console web interface or the @prisma/cli command-line tool [1][2][4]. Users deploy applications and manage configurations (including environment variables) via the CLI or the Console dashboard rather than a "Deploy Button" URL [2][8][3][9]. If you are trying to deploy a project that uses Prisma, you should: 1. Use the standard deployment platform workflows (such as Vercel's Deploy Button) to handle the application's hosting and git cloning [5][6][7]. 2. Use the Prisma Console to provision and manage your Prisma Postgres databases or Prisma Compute resources [4][10][11]. 3. Configure your environment variables (like DATABASE_URL) within your hosting provider's dashboard or via the Prisma CLI as instructed in the official Prisma guides [8][9][10][12].
Citations:
- 1: https://www.prisma.io/docs/compute/getting-started
- 2: https://www.prisma.io/docs/compute/deployments
- 3: https://www.prisma.io/docs/compute/cli-reference
- 4: https://www.prisma.io/docs/console
- 5: https://vercel.com/docs/deploy-button
- 6: https://vercel.com/docs/deploy-button/source
- 7: https://vercel.com/docs/deploy-button/environment-variables
- 8: https://www.prisma.io/docs/compute/environment-variables
- 9: https://www.prisma.io/docs/compute/faq
- 10: https://www.prisma.io/docs/prisma-orm/quickstart/prisma-postgres
- 11: https://www.prisma.io/docs/guides/postgres/netlify
- 12: https://www.prisma.io/docs/prisma-orm/add-to-existing-project/postgresql
Remove or replace the unsupported Deploy Button URL.
console.prisma.io/new/clone with repository-url and env matches Vercel’s Deploy Button contract, not a documented Prisma endpoint.
🤖 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-08-07.mdx` around lines 43 - 47, Remove the
unsupported Prisma Deploy Button URL block from the changelog entry, or replace
it with a documented Prisma endpoint and valid parameters. Do not retain the
`console.prisma.io/new/clone` link or its Vercel-style `repository-url` and
`env` query parameters.
| The first Prisma 8 release candidate is out, and an application now installs one Prisma package. Until now an app that talks to PostgreSQL installed a dozen `@prisma-next/*` packages; everything now arrives as dependencies of one database package under the `@prisma` scope. | ||
|
|
||
| ```jsonc | ||
| // package.json: the only Prisma dependency your app needs | ||
| { | ||
| "dependencies": { | ||
| "@prisma/orm-postgres": "8.0.0-rc.1" | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| Releases are now versioned `8.0.0-rc.N`, with no further `0.x` minors. Existing installs are not moved onto the release-candidate line by `npm update`: a `^0.x` range never matches a pre-release, so only a fresh install or an explicit version change lands on it. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Find manifests that still use the old package names and the new package.
rg -n -C 3 -g 'package.json' \
'"`@prisma-next/`|"`@prisma/orm-postgres`"' .Repository: prisma/web
Length of output: 148
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '%s\n' '--- changelog context ---'
sed -n '1,90p' apps/site/content/changelog/2026-08-07.mdx
printf '%s\n' '--- tracked references to package names ---'
git grep -n -E '`@prisma-next/`|`@prisma/orm-postgres`' -- ':!*.lock' || true
printf '%s\n' '--- tracked package manifests ---'
git ls-files '*package.json' | head -200Repository: prisma/web
Length of output: 35425
🏁 Script executed:
#!/bin/bash
set -euo pipefail
python3 - <<'PY'
from pathlib import Path
import json
import re
old = re.compile(r"^`@prisma-next/`")
new = "`@prisma/orm-postgres`"
manifests = []
for path in Path(".").rglob("package.json"):
try:
data = json.loads(path.read_text())
except Exception:
continue
deps = {}
for section in ("dependencies", "devDependencies", "optionalDependencies", "peerDependencies"):
deps.update(data.get(section, {}))
if any(old.match(name) for name in deps) or new in deps:
manifests.append((str(path), sorted(name for name in deps if old.match(name) or name == new)))
print("repository manifests with old/new Prisma dependency keys:")
for path, names in manifests:
print(f"{path}: {names}")
if not manifests:
print("(none)")
# The relevant npm invariant: update changes versions for existing keys.
existing = {"`@prisma-next/postgres`": "^0.16.0"}
updated = dict(existing)
updated["`@prisma-next/postgres`"] = "0.16.0"
print("unchanged dependency keys after an update:", sorted(updated))
print("new package added by update:", new in updated)
# A caret range beginning below 1.0.0 cannot include an 8.0.0 prerelease.
def caret_zero_upper(version):
major, minor, *_ = map(int, version.split("."))
return (0, minor + 1, 0)
lower = (0, 16, 0)
upper = caret_zero_upper("0.16.0")
candidate = (8, 0, 0)
print("candidate 8.0.0-rc.1 within ^0.16.0:", lower <= candidate < upper)
PYRepository: prisma/web
Length of output: 360
Document the package-name migration.
Existing installations must remove their @prisma-next/* dependencies and add @prisma/orm-postgres. npm update or reinstalling an unchanged manifest cannot rename dependencies or add the new package.
🤖 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-08-07.mdx` around lines 51 - 62, Update the
Prisma 8 release-candidate changelog entry to explicitly instruct existing
installations to remove all `@prisma-next/`* dependencies and add
`@prisma/orm-postgres` to package.json. Clarify that npm update or reinstalling an
unchanged manifest does not perform this package-name migration.
| ```bash | ||
| # Create a token; the value is returned once, never stored | ||
| curl -X POST https://api.prisma.io/v1/workspaces/$WORKSPACE/service-tokens \ | ||
| -H "Authorization: Bearer $TOKEN" -d '{"name":"ci"}' | ||
|
|
||
| # Revoke it | ||
| curl -X DELETE https://api.prisma.io/v1/workspaces/$WORKSPACE/service-tokens/$TOKEN_ID \ | ||
| -H "Authorization: Bearer $TOKEN" | ||
| ``` |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Inspect the generated endpoint documentation and locate its source operation.
sed -n '1,180p' \
apps/docs/content/docs/management-api/endpoints/service-tokens/post-workspaces-by-workspace-id-service-tokens.mdx
rg -n -C 5 -F '/v1/workspaces/{workspaceId}/service-tokens' .Repository: prisma/web
Length of output: 11618
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '%s\n' '--- candidate API specification files ---'
fd -HI -t f 'openapi|swagger|management-api|service-token' . | head -200
printf '%s\n' '--- request-body and content-type definitions ---'
rg -n -i -C 4 'service.?tokens|serviceToken|requestBody|application/json|content-type' \
--glob '!apps/docs/content/docs/management-api/endpoints/**' \
--glob '!node_modules/**' \
. | head -300Repository: prisma/web
Length of output: 25637
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '%s\n' '--- OpenAPI fetch and rendering configuration ---'
cat -n apps/docs/scripts/fetch-openapi.ts | sed -n '1,220p'
cat -n apps/docs/src/lib/openapi.ts | sed -n '1,220p'
printf '%s\n' '--- generated Postman operation ---'
rg -n -i -C 12 'service.?tokens|serviceToken|workspaceId' \
apps/docs/public/prisma-management-api.postman_collection.json | head -220
printf '%s\n' '--- all tracked management API assets ---'
git ls-files | rg -i 'management.*api|openapi|service.?token'Repository: prisma/web
Length of output: 50367
🏁 Script executed:
#!/bin/bash
set -euo pipefail
python3 - <<'PY'
import json
path = "apps/docs/public/prisma-management-api.postman_collection.json"
with open(path, encoding="utf-8") as f:
collection = json.load(f)
def walk(items):
for item in items:
request = item.get("request")
if request:
url = request.get("url", {})
parts = url.get("path", [])
if "service-tokens" in parts:
print(json.dumps({
"name": item.get("name"),
"method": request.get("method"),
"path": parts,
"headers": request.get("header"),
"body": request.get("body"),
}, indent=2))
walk(item.get("item", []))
walk(collection.get("item", []))
PY
printf '%s\n' '--- live OpenAPI operation content types ---'
curl --fail --silent --show-error https://api.prisma.io/v1/doc |
python3 -c '
import json, sys
doc = json.load(sys.stdin)
for path, item in doc.get("paths", {}).items():
if "service-tokens" in path:
print(json.dumps({"path": path, "post": item.get("post"), "delete": item.get("delete")}, indent=2))
'Repository: prisma/web
Length of output: 9137
Set the request content type to JSON.
The POST operation accepts application/json, but curl -d sends form-encoded data by default. Add -H "Content-Type: application/json" to the create-token command.
🤖 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-08-07.mdx` around lines 95 - 103, Add the
JSON Content-Type header to the POST create-token curl command, alongside its
existing Authorization header, so the request body is sent as application/json.
Leave the revoke command unchanged.
What
Adds the external changelog entry for 2026-08-03..2026-08-07 at
apps/site/content/changelog/2026-08-07.mdx, plus a Console template-catalog screenshot atapps/site/public/changelog/prisma-compute-template-catalog.png(captured from the live Console, cropped to exclude workspace names and account identity).Generated with
content-write-changelog(v2026.8.3) from a Loggy-style extraction (same repo discovery and PR window as Loggy's Extract step) for the same window. Loggy's Slack post was not available in the generating session.Review focus
Triage notes
Published with no public PR (private-repo work; confirm each capability is announced)
console.prisma.io/templates. The gate flagged in the 2026-08-02 entry's triage lifted this window./new/clone(Console, 1 PR) — no public docs page found; no badge image asset in the source material, so the snippet shows the bare URL contract. Snippet shape needs product review (example env var names are invented; the parameter grammar is from the source).devEngines, localhost-bind startup warning (Compute, 2 PRs).client_secret_postfix, template progress and clone-flow fixes, Object Store name-length fix.Flagged out of the entry
"@prisma/orm-postgres": "8.0.0-rc.1"in the package.json snippet: version composed from the release PRs (prisma/prisma#29918); confirm the RC is published under that exact version.Excluded (public repos)
DRIVER.PREPARE_FAILEDdetail (the Breaking callout covers the interface change).Screenshot
The image is committed to
public/changelog/with a plain filename rather than the CMS-hashed pattern used by older entries; rename or re-upload through the CMS if that pipeline is preferred.🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Improvements
Security