chore(deps): @prisma/management-api-sdk ^1.79.0 -> ^1.80.0

[wmadden-electric]

Moves @prisma/management-api-sdk from ^1.79.0 to ^1.80.0 in the five packages that declare it. The lockfile now resolves only 1.80.0.

SDK 1.80.0 types credential.type in the GET /v1/me response as "oauth" | "service_token" | "management_token" | "agent_token" again, after prisma/pdp-control-plane#5487 restored the enum. Versions 1.75.0 to 1.79.0 typed it as string. Composer does not depend on that field, so no source code changed.

The Prisma CLI moves to the same version in prisma/prisma-cli#315. With both on one version, an install resolves one copy of the SDK.

Verified locally: build, typecheck, lint, lint:deps, unit tests, test:types, test:scripts, check:publish-deps, check:cli-engine-pin and check:orm-pins. Many test tasks were served from the turbo cache, so CI is the full run.

🤖 Generated with Claude Code

[prisma-gizmo]

✅ Gizmo reviewed 1a89fd9 — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

This PR bumps @prisma/management-api-sdk from ^1.79.0 to ^1.80.0 in the five workspace packages that declare it (examples/orm-demo, lowering, composer-prisma-cloud, composer, and website), so the restored credential.type enum from SDK 1.80.0 is picked up and Composer lands on the same SDK version the CLI is moving to, letting a single install resolve one copy of the package.

Dependency consistency. Every package.json in the workspace that declares the SDK is covered — a repo-wide search finds no other manifest referencing it, and there is no catalog: entry for the SDK in pnpm-workspace.yaml, so the five manifests plus the lockfile are the complete surface. The regenerated pnpm-lock.yaml resolves 1.80.0 for all five importers with no duplicate copies, and the lockfile's importer specifiers match the manifests.

Pin-policy fit. The caret specifier is deliberate rather than an oversight: scripts/check-publish-deps.mjs only enforces exact pins on dependencies that belong to this workspace and explicitly names @prisma/management-api-sdk as an external package sharing the @prisma/ scope, so ^1.80.0 in shipped dependencies is the correct form. @prisma/cli-engine's peer range (^1.55.0) also remains satisfied.

Source impact. None — no workspace source reads credential.type from the GET /v1/me response, which is the only typing change in 1.80.0 relative to the 1.79.x string typing, so the PR correctly ships manifest and lockfile updates only.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: d6f673fb-387a-4422-a510-f45ae3eadd01

---

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

[prisma-gizmo]

New findings: none · trace

[prisma-gizmo]

All Gizmo review threads are resolved and the head commit has been reviewed. Approving.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@prisma/composer@317

npm i https://pkg.pr.new/@prisma/composer-cli@317

npm i https://pkg.pr.new/@prisma/composer-prisma-cloud@317

commit: 1a89fd9