Repository navigation
Bump to version 8.0.0-rc.29 - #379
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
commit: |
wmadden
approved these changes
Oct 30, 2026
wmadden
pushed a commit
that referenced
this pull request
Nov 3, 2026
`npx prisma dev` fails for every new Composer project today: ```text ERROR: @prisma/composer-prisma-cloud: invalid container transport payload — "input.environment" is not a string. ``` This PR releases 8.0.0-rc.30, which fixes it. The fix is already on `main` (#378); it has not been released. ## Why it fails `prisma` 8.0.0-rc.29 bundles Composer 0.35.0. Composer 0.36.0 came out yesterday, and the getting-started page's `npm install @prisma/composer @prisma/composer-prisma-cloud` installs it. The CLI's 0.35.0 and the project's 0.36.0 disagree on the data they pass to each other, so `prisma dev` stops before anything starts. #378 moves the CLI to Composer 0.36.0. ## What users see change Composer 0.36.0 renames a stage to an environment: - `prisma deploy --environment <name>` replaces `--stage`. - `--stage` now fails with `CLI.COMMAND_MOVED`, naming the replacement. `prisma dev`, `dev url` and `dev stop` also take `--environment`, and each environment runs its own local copy. `prisma dev` reads secrets from the environment and no longer invents placeholder values. The docs, `prisma/cloud-deploy-action` and `create-prisma` follow in their own PRs, after this release. ## How it was checked - I packed the `prisma` package from #378's branch and installed it with Composer 0.36.0 into the Composer getting-started app. `prisma dev` reached ready, the gateway answered with a quote, and the direct call to the quotes service got the 401 the page expects. - `prisma deploy --stage x` failed with `CLI.COMMAND_MOVED`, naming `--environment`. ## Release Previous version 8.0.0-rc.29, new version 8.0.0-rc.30. See [docs/oss/versioning.md](docs/oss/versioning.md). **Merging this PR ships the release**: the push to `main` changes the root version, the `Publish to npm` workflow publishes `@prisma/cli-engine` and then `@prisma/cli` and `prisma` under `latest`, and creates a pre-release GitHub Release with generated notes. The diff touches the same files as the rc.29 release (#379). Agent: janeway-45 🤖 Generated with [Claude Code](https://claude.com/claude-code) Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
npx prisma@latest orm initfails on every new project today. It exits 5:This PR releases 8.0.0-rc.29, which fixes it. The fix is already on
main(#375); it has not been released.Why it fails
prisma8.0.0-rc.28 pins@prisma/orm-toolchain8.0.0-rc.20. That toolchain's startercontract.prismawritesupdatedAt temporal.updatedAtString().orm initthen installs@prisma/orm-postgres@^8.0.0-rc.21, which removed field presets, so the emit step rejects the starter it was just given. #375 moved the toolchain to 8.0.0-rc.21, whose starter writestemporal.UpdatedAtString.How it was checked
In an empty folder outside any workspace, with npm as the package manager:
npx prisma@8.0.0-rc.28 orm init --yes --target postgres --authoring pslexits 5 with the error above.updatedAtlines totemporal.UpdatedAtString(what the rc.21 toolchain writes) and runningnpx prisma contract emitexits 0 and writescontract.jsonandcontract.d.ts.temporal.UpdatedAtStringin all four starters; rc.20 containstemporal.updatedAtString().Release
Previous version 8.0.0-rc.28, new version 8.0.0-rc.29. See docs/oss/versioning.md. Merging this PR ships the release: the push to
mainchanges the root version, thePublish to npmworkflow publishes@prisma/cli-engineand then@prisma/cliandprismaunderlatest, and creates a pre-release GitHub Release with generated notes.The diff touches the same files as the rc.28 release (#372).
Agent: seacole-52
🤖 Generated with Claude Code