Merge branch 'main' into feat/getting-started-revamp

Author: ankur-arch

apps/docs/public/prisma-management-api.postman_collection.json

@@ -0,0 +1,96 @@
+---
+title: "Store files with Object Store buckets and see your workspace at a glance"
+date: "2026-07-24"
+version: "2026-07-24"
+slug: "2026-07-24"
+headline: "Store files with Object Store buckets and see your workspace at a glance"
+tags:
+  - "Prisma"
+  - "Prisma Compute"
+  - "Prisma Next"
+canonical: "/changelog#log2026-07-24"
+metaDescription: "Object Store buckets bring S3-compatible file storage to Prisma projects, the Console workspace page becomes an overview dashboard, and Prisma Next 0.16.0 lands on npm."
+share:
+  active: true
+  content: "Look at this page: "
+---
+Prisma projects can now store files. Object Store buckets are S3-compatible storage that lives next to your Prisma Postgres databases and Prisma Compute apps, managed from the Prisma Console, the Management API, or MCP tools.
+
+The Prisma Console workspace page is now an overview dashboard: usage against your plan, the current invoice, deploy health, and your most active projects on one screen.
+
+Prisma Next 0.16.0 is on npm, and bringing an existing database to Prisma Next is now much smoother. The prisma.io docs are also rebuilt for coding agents, with per-section `llms.txt` indexes and a markdown version of every page.
+
+## Highlights
+
+### New · Store files in your project with Object Store buckets
+
+Apps that store user uploads or generated files needed a separate storage vendor, with its own account, credentials, and billing. Every Prisma project can now create Object Store buckets: S3-compatible storage that lives alongside your databases and apps. Create a bucket in the Prisma Console, generate an access key (the secret is shown exactly once, so store it safely), and read and write objects with any S3 client or SDK.
+
+Buckets can also be managed through the new `/v1/buckets` [Management API endpoints](https://www.prisma.io/docs/management-api/endpoints/buckets/get-buckets) and matching MCP tools, so agents can provision storage the same way they provision databases. Deleting a bucket removes its contents in one step, even when it is not empty.
+
+### New · See your whole workspace at a glance
+
+The Console landing page used to show a usage dashboard, so answering "is everything healthy?" meant clicking through projects. The workspace page is now an overview: billing-cycle usage with your included-limit line, the current invoice with per-line meters, and your top projects with their deploy health, repository, latest commit, and share of usage. The detailed usage dashboard, including usage-threshold and database-quota alerts, moved to its own Usage page, and the projects list is now paginated.
+
+### New · Prisma Next 0.16.0
+
+Pointing Prisma Next at an existing database could produce a schema its own toolchain rejected: `contract infer` printed output that `contract emit` refused, index types like `gin` failed to emit, and a column's exact type and its auto-update behavior could not be declared together. In 0.16.0, inferred schemas work as generated: infer output round-trips cleanly through emit, the built-in Postgres index types (`gin`, `gist`, `brin`, and friends) emit, and new temporal presets let one field declaration carry both the column type and its auto-update behavior:
+
+```prisma
+model Page {
+  updatedAt temporal.timestamp(3, onCreate: now, onUpdate: now)
+  lastSeen  temporal.timestamp(3)
+  touched   temporal.timestamptz(onUpdate: now)
+}
+```
+
+> **Note:** Prisma Next is in Early Access. Scope and behavior may still change. This release includes breaking changes, listed below.
+
+Read the [v0.16.0 release notes](https://github.com/prisma/prisma-next/releases/tag/v0.16.0) for the full list. Shipped in [prisma/prisma-next#1003](https://github.com/prisma/prisma-next/pull/1003), [prisma/prisma-next#1011](https://github.com/prisma/prisma-next/pull/1011), and [prisma/prisma-next#1019](https://github.com/prisma/prisma-next/pull/1019).
+
+## Prisma Next
+
+Beyond the 0.16.0 headline changes, your editor now gives live schema feedback, and polymorphic queries get more capable.
+
+- **New** · Schema problems show up in your editor as you type. The language server now reports unresolvable relations, type and codec mismatches, and extension-block errors live, instead of waiting for `contract emit`. If your config file fails to load, the error appears on the config file itself, and existing diagnostics stay put instead of disappearing. ([prisma/prisma-next#972](https://github.com/prisma/prisma-next/pull/972), [prisma/prisma-next#974](https://github.com/prisma/prisma-next/pull/974))
+- **Improved** · Polymorphic queries can follow relations declared on a variant: narrow a query with `.variant(...)` and `.include()` the relations that variant declares. ([prisma/prisma-next#976](https://github.com/prisma/prisma-next/pull/976))
+
+<details>
+<summary>Fixes and improvements (4)</summary>
+
+- **Fixed** · A `Bytes` column selected inside `.include()` now returns bytes instead of raw `\x...` hex text. ([prisma/prisma-next#942](https://github.com/prisma/prisma-next/pull/942))
+- **Fixed** · Migrations run their operations in dependency order, fixing cases such as a column being dropped before its own constraint. ([prisma/prisma-next#992](https://github.com/prisma/prisma-next/pull/992))
+- **Fixed** · Count-returning updates and deletes on a narrowed variant no longer generate SQL that references a missing table. ([prisma/prisma-next#940](https://github.com/prisma/prisma-next/pull/940))
+- **Fixed** · More `contract infer` fixes: `Decimal` fields connect without a codec error, `dbgenerated(...)` defaults no longer report permanent drift in `db verify`, and foreign keys that point outside the introspected tables are explained in the output instead of silently dropped. ([prisma/prisma-next#1011](https://github.com/prisma/prisma-next/pull/1011))
+</details>
+
+## Prisma Compute
+
+App detection moved into the public SDK, and app URLs are now correct before your first deploy.
+
+- **New** · The Prisma Compute SDK can inspect a repository without cloning it: `detectComputeApp` reads a repository snapshot and reports the app's framework, build type, HTTP port, and entrypoint. Elysia, Express, and Fastify apps are recognized and run on Bun. Available since `@prisma/compute-sdk` 0.37.0.
+- **Improved** · The GitHub repository picker in the Prisma Console loads repositories page by page, so installations with more than 100 repositories can reach all of them, and switching accounts mid-load no longer briefly shows the wrong account's list.
+- **Fixed** · The app URL returned before your first deployment now names the domain your app will actually serve on. Previously it could point at the wrong region and never resolve.
+
+## Prisma docs
+
+The prisma.io docs are now built for coding agents.
+
+- **New** · The root `llms.txt` is a compact index linking ten per-section indexes instead of one file too large for agents to read, every page carries a crawler-visible pointer to its markdown version, and MCP server discovery is published. Point your agent at [prisma.io/docs](https://www.prisma.io/docs) and every page is reachable from the root index. ([prisma/web#8087](https://github.com/prisma/web/pull/8087))
+- **New** · A [Plasmic integration guide](https://www.prisma.io/docs/guides/integrations/plasmic) walks through connecting a Plasmic-built React app to Prisma, with queries configured visually in Plasmic Studio and credentials staying in your app's environment. ([prisma/web#8095](https://github.com/prisma/web/pull/8095))
+
+## Breaking changes
+
+> ⚠️ **Breaking:** Prisma Next 0.16.0 changes the emitted contract shape. Foreign keys and their backing indexes are now separate contract entries, a 1:1 relation over a non-unique foreign key fails emit with `PSL_NON_UNIQUE_BACKRELATION`, `contract infer` declares identity-column defaults, and inferred back-relation names no longer double-pluralize. Your database schema is unaffected. To migrate, re-run `contract emit` and follow the [0.15-to-0.16 upgrade recipe](https://github.com/prisma/prisma-next/blob/v0.16.0/skills/upgrade/prisma-next-upgrade/upgrades/0.15-to-0.16/). ([prisma/prisma-next#989](https://github.com/prisma/prisma-next/pull/989), [prisma/prisma-next#1015](https://github.com/prisma/prisma-next/pull/1015), [prisma/prisma-next#1011](https://github.com/prisma/prisma-next/pull/1011))
+
+> ⚠️ **Breaking:** The deprecated experimental `/v1/compute-services` and `/v1/versions` Management API endpoints are removed. To migrate, use the [`/v1/apps` and `/v1/deployments` endpoints](https://www.prisma.io/docs/management-api), which cover the same operations.
+
+## Guides and articles
+
+- [Extending Prisma Next with Typed Postgres ltree](https://www.prisma.io/blog/prisma-next-ltree-extension): use PostgreSQL `ltree` in Prisma Next with `prisma-ltree`, with typed path columns plus ancestor and descendant queries.
+- [You Don't Need Elasticsearch, Postgres Already Has Full-Text Search](https://www.prisma.io/blog/you-dont-need-elasticsearch-postgres-already-has-full-text-search): build full-text search with `tsvector`, GIN indexes, and `pg_trgm` typo tolerance on Prisma Postgres.
+- [How to Make Your Docs Agent-Ready](https://www.prisma.io/blog/make-your-docs-agent-ready): coding agents fail silently on truncated indexes, broken links, and missing metadata. What we fixed in the Prisma docs, and how to audit yours.
+
+---
+
+_Need help applying these changes in production? [Prisma Enterprise Support](https://prisma.io/enterprise) can help with schema design, performance, security, and compliance._

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

@@ -20,6 +20,7 @@
     "@prisma/eclipse": "workspace:^",
     "@react-three/fiber": "^9.5.0",
     "cobe": "^2.0.1",
+    "codehike": "^1.1.0",
     "cors": "^2.8.6",
     "fumadocs-core": "catalog:",
     "fumadocs-mdx": "catalog:",

apps/site/package.json

@@ -0,0 +1,50 @@
+"use client";
+
+import { cn } from "@/lib/cn";
+import { useRef, useState } from "react";
+
+/**
+ * The primary CTA: the scaffold command with a copy button. The command is
+ * plain text in the DOM (crawlable, selectable); the button is labelled and
+ * announces success politely.
+ */
+export function CopyCommand({ command, className }: { command: string; className?: string }) {
+  const [copied, setCopied] = useState(false);
+  const timer = useRef<ReturnType<typeof setTimeout> | undefined>(undefined);
+
+  const copy = async () => {
+    try {
+      await navigator.clipboard.writeText(command);
+      setCopied(true);
+      clearTimeout(timer.current);
+      timer.current = setTimeout(() => setCopied(false), 2000);
+    } catch {
+      // Clipboard can be unavailable (permissions, http); the text stays selectable.
+    }
+  };
+
+  return (
+    <div
+      className={cn(
+        "flex items-center gap-3 rounded-square-high border border-stroke-neutral bg-background-neutral-weaker py-2.5 pl-4 pr-2.5",
+        className,
+      )}
+    >
+      <code className="font-mono text-sm text-foreground-neutral md:text-base">
+        <span className="select-none text-foreground-neutral-weaker">$ </span>
+        {command}
+      </code>
+      <button
+        type="button"
+        onClick={copy}
+        aria-label={`Copy the command ${command}`}
+        className="grid size-8 shrink-0 place-items-center rounded-square border border-stroke-neutral text-foreground-neutral-weak transition-colors hover:border-stroke-ppg hover:text-foreground-ppg"
+      >
+        <i className={copied ? "fa-regular fa-check" : "fa-regular fa-copy"} aria-hidden />
+      </button>
+      <span aria-live="polite" className="sr-only">
+        {copied ? "Command copied to clipboard" : ""}
+      </span>
+    </div>
+  );
+}

apps/site/public/og/og-stack.png

@@ -0,0 +1,68 @@
+import { BunMark } from "./bun-mark";
+import { PrismaMark } from "./prisma-mark";
+import styles from "./stack.module.css";
+
+const heroLayers = [
+  {
+    id: "app",
+    eyebrow: "You write",
+    title: "Your application",
+    icon: <i className="fa-regular fa-laptop" aria-hidden />,
+    accent: "violet" as const,
+  },
+  {
+    id: "orm",
+    eyebrow: "Talks through",
+    title: "Prisma ORM",
+    icon: <PrismaMark className="size-[14px]" />,
+    accent: "orm" as const,
+  },
+  {
+    id: "postgres",
+    eyebrow: "Stores in",
+    title: "Prisma Postgres",
+    icon: <i className="fa-regular fa-database" aria-hidden />,
+    accent: "ppg" as const,
+  },
+  {
+    id: "compute",
+    eyebrow: "Runs on",
+    title: "Prisma Compute + Bun",
+    icon: <BunMark className="size-[15px]" />,
+    accent: "ppg" as const,
+  },
+];
+
+/**
+ * The hero's animated stack: the four layers enter staggered, then a request
+ * pulse travels the connectors on a loop. The layers widen toward the base so
+ * the visual previews the stack pyramid the reader meets one scroll later.
+ * Pure CSS, server-rendered; under prefers-reduced-motion everything is
+ * simply visible and static, so the relationship reads the same without
+ * animation.
+ */
+export function HeroVisual() {
+  return (
+    <div className={styles["hero-visual"]} aria-hidden>
+      {heroLayers.map((layer, index) => (
+        <div
+          key={layer.id}
+          className={styles["hero-layer-slot"]}
+          style={{ "--row": index } as React.CSSProperties}
+        >
+          {index > 0 && <span className={styles["hero-connector"]} />}
+          <div
+            className={`${styles["hero-layer"]} ${styles[`accent-${layer.accent}`]}`}
+            style={{ animationDelay: `${index * 140}ms` }}
+          >
+            <span className={styles["hero-layer-icon"]}>{layer.icon}</span>
+            <span className={styles["hero-layer-text"]}>
+              <span className={styles["hero-layer-eyebrow"]}>{layer.eyebrow}</span>
+              <span className={styles["hero-layer-title"]}>{layer.title}</span>
+            </span>
+          </div>
+        </div>
+      ))}
+    </div>
+  );
+}

apps/site/src/app/stack/copy-command.tsx

@@ -0,0 +1,68 @@
+import { prisma_highlighter } from "@/lib/shiki_prisma";
+import type { HighlightedCode } from "codehike/code";
+import type { CSSProperties } from "react";
+import { journeySteps, type JourneyStep } from "./journey-steps";
+
+/** Code Hike token: plain text, or [text, color, style?]. */
+type CodeToken = string | [string, string, CSSProperties?];
+
+/**
+ * Tokenize with the site's shiki `prisma-dark` theme (CSS-variable colors, so
+ * it adapts to both themes) and re-shape into Code Hike's token format. Tokens
+ * are split per word because Code Hike's transitions move tokens
+ * independently; coarser tokens make the animation lurch.
+ */
+function toCodeTokens(text: string, color: string, out: CodeToken[]) {
+  for (const part of text.split(/(\s+)/)) {
+    if (!part) continue;
+    if (/^\s+$/.test(part)) {
+      out.push(part);
+    } else {
+      out.push([part, color]);
+    }
+  }
+}
+
+async function highlightStep(code: string, lang: JourneyStep["lang"]): Promise<HighlightedCode> {
+  const tokens: CodeToken[] = [];
+  if (lang === "text") {
+    // Plain-text steps (the project tree): names in the normal code color,
+    // trailing `# …` annotations dimmed like comments.
+    code.split("\n").forEach((line, index) => {
+      if (index > 0) tokens.push("\n");
+      const hash = line.indexOf("# ");
+      if (hash > -1) {
+        toCodeTokens(line.slice(0, hash), "var(--color-foreground-neutral-weak)", tokens);
+        toCodeTokens(line.slice(hash), "var(--color-disabled)", tokens);
+      } else {
+        toCodeTokens(line, "var(--color-foreground-neutral-weak)", tokens);
+      }
+    });
+  } else {
+    const highlighter = await prisma_highlighter();
+    const lines = highlighter.codeToTokensBase(code, {
+      lang,
+      theme: highlighter.getTheme("prisma-dark"),
+    });
+    lines.forEach((line, index) => {
+      if (index > 0) tokens.push("\n");
+      for (const token of line) {
+        toCodeTokens(token.content, token.color ?? "currentColor", tokens);
+      }
+    });
+  }
+  return {
+    tokens,
+    code,
+    lang,
+    meta: "",
+    themeName: "prisma-dark",
+    style: {},
+    annotations: [],
+  } as unknown as HighlightedCode;
+}
+
+/** Highlight every journey step on the server; the player receives plain data. */
+export async function highlightJourney(): Promise<HighlightedCode[]> {
+  return Promise.all(journeySteps.map((step) => highlightStep(step.code, step.lang)));
+}