Repository navigation
Bump to version 8.0.0-rc.30 - #380
Open
wmadden-electric wants to merge 1 commit into
Open
wmadden-electric wants to merge 1 commit into
wmadden-electric wants to merge 1 commit into
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>
|
Warning Review limit reachedThis review ran on the open-source allowance, not this organization's plan, because the pull request author doesn't have an assigned seat. Waiting won't change this — ask an organization admin to assign them a seat, or add seats in Billing if every seat is already assigned, then retry. Next included review available in 48 minutes. View limit details
Comment |
commit: |
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 devfails for every new Composer project today: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
prisma8.0.0-rc.29 bundles Composer 0.35.0. Composer 0.36.0 came out yesterday, and the getting-started page'snpm install @prisma/composer @prisma/composer-prisma-cloudinstalls it. The CLI's 0.35.0 and the project's 0.36.0 disagree on the data they pass to each other, soprisma devstops 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.--stagenow fails withCLI.COMMAND_MOVED, naming the replacement.prisma dev,dev urlanddev stopalso take--environment, and each environment runs its own local copy.prisma devreads secrets from the environment and no longer invents placeholder values.The docs,
prisma/cloud-deploy-actionandcreate-prismafollow in their own PRs, after this release.How it was checked
prismapackage from Follow the products' released versions: @prisma/composer-cli 0.35.0 -> 0.36.0; @prisma/composer 0.35.0 -> 0.36.0 #378's branch and installed it with Composer 0.36.0 into the Composer getting-started app.prisma devreached ready, the gateway answered with a quote, and the direct call to the quotes service got the 401 the page expects.prisma deploy --stage xfailed withCLI.COMMAND_MOVED, naming--environment.Release
Previous version 8.0.0-rc.29, new version 8.0.0-rc.30. 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.29 release (#379).
Agent: janeway-45
🤖 Generated with Claude Code