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

[wmadden-electric]

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

The Prisma CLI consumes @prisma/composer and pins the SDK to 1.79.0 in prisma/prisma-cli#290. With both on the same version, an install resolves one copy of the SDK instead of two.

No source code changed. The one type change in the SDK between these versions that is not an addition is credential.type in the GET /v1/me response, which went from a three-value union to string. Composer does not depend on it.

Verified locally: build, typecheck, lint, lint:deps, unit tests, test:types, test:scripts, check:publish-deps, check:cli-engine-pin and check:orm-pins.

🤖 Generated with Claude Code

[prisma-gizmo]

✅ Gizmo reviewed 66ba8d9 — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

This PR bumps @prisma/management-api-sdk from ^1.76.0 to ^1.79.0 in the five workspace manifests that declare it (examples/orm-demo, lowering, composer-prisma-cloud, composer, website). The motivation is deduplication with the Prisma CLI, which pins the SDK at 1.79.0 in a companion PR; with matching specs an install resolves a single SDK copy instead of two.

Dependency consistency. The lockfile update rides along in the same commit (skipped from the checklist as generated) and confirms the outcome: every importer's ^1.79.0 specifier resolves to exactly one 1.79.0 copy, with no residual 1.76.x resolution. The SDK's own consumers remain compatible — @prisma/cli-engine@0.6.1 declares a ^1.55.0 peer range on the SDK, which 1.79.0 satisfies.

Publish-facing implications. The two publishable packages (@prisma/composer and @prisma/composer-prisma-cloud) ship the SDK as a caret dependencies entry. That is the compliant form: the check-publish-deps exact-pin rule applies only to internal workspace packages, and its comment explicitly names @prisma/management-api-sdk as an external package in the shared @prisma/ npm scope that must not be treated as internal. The three other bump sites are private (the two examples and the website), so their specs never reach a tarball.

Type-surface risk. No source code changed. The SDK's only non-additive change between 1.76.0 and 1.79.0 — credential.type in the GET /v1/me response widening from a three-value union to string — is not read anywhere in the workspace (the SDK is consumed via createManagementApiClient and the derived operations/paths types in lowering/src/builds, container.ts, and the website's verify-deployed.ts), so widening cannot break workspace typechecks.

[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: ad5af6cf-eb6c-44c0-9e25-23248d2717ce

---

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

[pkg-pr-new]

Open in StackBlitz

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

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

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

commit: 66ba8d9

[prisma-gizmo]

New findings: none · trace

[prisma-gizmo]

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