v0.15.0

What's Changed

• Composer deploys become replay-only: schema synthesis leaves the deploy pipeline by @wmadden-electric in #259
• Teach the replay-only workflow in the shipped agent skill by @wmadden-electric in #260
• Test against @prisma/dev 0.25.2, which recovers from a crashed holder by @wmadden-electric in #261
• fix(prisma-cloud): attach production databases to the default Branch by @kristof-siket in #258
• fix(deps): pin effect to 4.0.0-rc.112 and add sql companions by @kristof-siket in #264
• Release 0.15.0: ORM family to 8.0.0-rc.8, engine to 0.3.0 by @wmadden-electric in #263

Full Changelog: v0.14.0...v0.15.0

v0.14.0

What's Changed

• chore(release): v0.14.0 by @wmadden-electric in #257

Full Changelog: v0.13.0...v0.14.0

v0.13.0

What's Changed

• chore(release): v0.13.0 by @wmadden-electric in #256

Full Changelog: v0.12.0...v0.13.0

v0.12.0

What's Changed

• Ship the prisma-composer skill inside the @prisma/composer tarball by @wmadden-electric in #251
• Submit the application topology per deploy and stamp the build with its content hash by @wmadden-electric in #252
• Retire destroy and log from the composer command family by @wmadden-electric in #253
• Adopt alchemy 2.0.0-beta.74: upstream buckets, Deployment.triggers, patches retired by @wmadden-electric in #254
• chore(release): v0.12.0 by @wmadden-electric in #255

Full Changelog: v0.11.0...v0.12.0

v0.11.0

What's Changed

• feat(cli): discover prisma-composer.config.{mts,mjs,js} alongside the .ts spelling by @kristof-siket in #248
• chore: migrate the biome config to 2.5.4 and format the version-utils test by @kristof-siket in #240
• fix(node): stage the files bun-conditional exports resolve to in the directory form by @kristof-siket in #250
• feat: adopt the upstream alchemy/Prisma provider by @wmadden-electric in #197
• fix(dev-emulators): read class-shaped Prisma Dev registry by @AmanVarshney01 in #246
• chore(release): v0.11.0 by @kristof-siket in #249

Full Changelog: v0.10.0...v0.11.0

v0.10.0

What's Changed

• Release 0.10.0: composer-prisma-cloud moves to orm-toolchain 8.0.0-rc.4 by @wmadden-electric in #245

Full Changelog: v0.9.0...v0.10.0

v0.9.0

What's Changed

• The dev-version counter is a tested pure function by @wmadden-electric in #239
• A release push also publishes a dev build by @wmadden-electric in #241
• fix(cli): resolve .js and extensionless relative imports to .ts under Node by @kristof-siket in #238
• chore(release): v0.9.0 by @kristof-siket in #243

Full Changelog: v0.8.0...v0.9.0

v0.8.0

What's Changed

• Release 0.8.0: the engine peer moves to @prisma/cli-engine@0.2.0 by @wmadden-electric in #237

Full Changelog: v0.7.0...v0.8.0

v0.7.0

What's Changed

• fix(ci): one-off docs-site state migration to the branch-id scope (TML-3157) by @wmadden-electric in #199
• chore(ci): remove the one-off TML-3157 docs state migration by @wmadden-electric in #200
• docs: drop the redundant --skill flag from the install command by @wmadden-electric in #201
• fix(cli): fail at start-up on a mismatched effect version instead of crashing inside alchemy by @wmadden-electric in #202
• fix(prisma-cloud): bound the last three Management API listing loops by @wmadden-electric in #204
• feat(deps): upgrade alchemy to beta.67 and effect to beta.103 by @wmadden-electric in #203
• fix(prisma-cloud): scope the env-var adoption lookup to the deploy's branch by @kristof-siket in #207
• feat(cli): programmatic control API — @prisma/composer/control (TML-3174) by @wmadden-electric in #205
• docs(adr): rewrite ADR-0044 for fresh-eyes readers by @wmadden-electric in #208
• feat(prisma-cloud): deploy state moves behind the platform Alchemy state API, with a deploy lease by @wmadden-electric in #209
• fix: FT-5226's socket-drop shape kills the canary and could kill a deploy by @wmadden-electric in #211
• chore: upgrade Prisma Next to the @prisma/* 8.0.0-rc.1 packages by @wmadden-electric in #212
• fix(ci): stop three timing races failing unrelated PRs by @wmadden-electric in #213
• fix(ci): space the cold-connect canary's samples so a warm database can't look like a fix by @wmadden-electric in #214
• Composer's CLI becomes four commands on the Prisma CLI engine by @wmadden-electric in #220
• Node 22 is enough, and the engine pin catches up by @wmadden-electric in #224
• fix(composer): move @effect/vitest from dependencies to devDependencies by @kristof-siket in #225
• CI imports every published entrypoint on the Node floor it advertises by @wmadden-electric in #226
• Split @prisma/composer into the library and @prisma/composer-cli; the engine becomes an exact peer by @wmadden-electric in #229
• feat(prisma-cloud): resolve the deploy target by project logical id by @kristof-siket in #230
• Adopt @prisma/cli-engine 0.1.0 by @wmadden-electric in #234
• feat: report every deploy to Prisma Cloud as a Build by @wmadden-electric in #227
• fix(compute): deploy standard framework output by @AmanVarshney01 in #235
• chore(release): v0.7.0 by @wmadden-electric in #236

New Contributors

• @kristof-siket made their first contribution in #207
• @AmanVarshney01 made their first contribution in #235

Full Changelog: v0.6.0...v0.7.0

v0.6.0

What's Changed

• fix(prisma-cloud): create Projects without the platform default database by @wmadden-electric in #194
• fix(deps): pin effect and its companion packages so standalone npm installs get one working effect by @wmadden-electric in #196
• fix(deploy): scope deploy state by the target Branch id, never the OS username by @wmadden-electric in #195
• chore(release): v0.6.0 by @wmadden-electric in #198

Full Changelog: v0.5.0...v0.6.0