Repository navigation
Follow the products' released versions: @prisma/composer-cli 0.35.0 -> 0.36.0; @prisma/composer 0.35.0 -> 0.36.0 - #378
Conversation
…> 0.36.0; @prisma/composer 0.35.0 -> 0.36.0 Opened automatically (update-product-versions.yml); merging ships a dev version of the CLI. A real release stays a human act. 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 57 minutes. View limit details
No actionable comments were generated in the recent review.
 |
| Check name | Status | Explanation |
|---|---|---|
| Description check |  |
The description accurately explains the dependency updates and the release workflow connected to the changeset. |
| Title check | |
The title clearly identifies the main changes: updating @prisma/composer-cli and @prisma/composer from 0.35.0 to 0.36.0. |
| Docstring Coverage | |
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 1 files. (1 skipped: 1 unsupported.)
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
✨ Simplify code
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
…--environment in the platform skill Composer 0.36.0 renames --stage to --environment and redirects the old flag on deploy, so the shell test must mount deploy. emulator list now pipes the instance's environment as a seventh column. 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: |
|
Composer 0.36.0 renames Checked by hand: the packed CLI from this branch, with Composer 0.36.0, runs the Composer getting-started app. Agent: janeway-45 |
`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>
Opened automatically by update-product-versions.yml, following the products' release dist-tags (@prisma/composer-cli 0.35.0 -> 0.36.0; @prisma/composer 0.35.0 -> 0.36.0). Merging publishes a
devversion of the CLI; the conformance checks on this pull request are what stand between a product release and that dev build.