Skip to content

Follow the products' released versions: @prisma/composer-cli 0.35.0 -> 0.36.0; @prisma/composer 0.35.0 -> 0.36.0 - #378

Merged
prisma-bot merged 3 commits into
mainfrom
product-versions/20261030062951
Oct 30, 2026
Merged

prisma-bot merged 3 commits into
mainfrom
product-versions/20261030062951

Conversation

@prisma-bot

Copy link
Copy Markdown
Collaborator

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 dev version of the CLI; the conformance checks on this pull request are what stand between a product release and that dev build.

…> 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>
@prisma-bot
prisma-bot enabled auto-merge (squash) October 30, 2026 06:29
@coderabbitai

coderabbitai Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Warning

Review limit reached

This 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.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 999c0c86-bdd5-486f-b9a4-494f5ea03170
Commits

Reviewing files that changed from the base of the PR and between a8d271e and a3c8329.

Files ignored due to path filters: 1
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing: 4
  • packages/cli/package.json
  • packages/cli/tests/composer-mount.test.ts
  • packages/prisma/package.json
  • skills/prisma-platform-core-concepts/SKILL.md

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: be25412c-701e-4f5c-a2a3-bc92436536c8
Commits

Reviewing files that changed from the base of the PR and between ffbed6f and a8d271e.

Files selected for processing: 2
  • packages/cli/tests/composer-mount.test.ts
  • skills/prisma-platform-core-concepts/SKILL.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Summary by CodeRabbit

  • Documentation
    • Updated guidance to use “environment” terminology when creating and targeting preview branches, listing deployed nodes, and deploying shareable previews.
  • Chores
    • Updated supporting tooling for the command-line tools and Prisma package. No additional end-user behavior changes are noted.

Walkthrough

The CLI and Prisma package manifests update Composer dependencies from version 0.35.0 to 0.36.0. The Composer emulator test adds the dev environment label, includes the deploy command path, and expects the environment in emulator-list output. The CLI skill replaces --stage terminology with --environment in preview and deployment instructions.

Priority: Pending latest changes

Merge Risk: Minimal · previous review a8d27

No merge-blocking issue is identified in the Composer upgrade and environment terminology updates. Merge after normal checks pass.

Pre-merge checks: Passed 5
Check name Status Explanation
Description check Passed The description accurately explains the dependency updates and the release workflow connected to the changeset.
Title check Passed The title clearly identifies the main changes: updating @prisma/composer-cli and @prisma/composer from 0.35.0 to 0.36.0.
Docstring Coverage Passed 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 Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed 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.

…--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>
@pkg-pr-new

pkg-pr-new Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

npx https://pkg.pr.new/@prisma/cli@378
npx https://pkg.pr.new/@prisma/cli-engine@378

commit: a3c8329

@wmadden-electric

Copy link
Copy Markdown
Contributor

Composer 0.36.0 renames --stage to --environment and adds a redirect on deploy for the old flag. The engine refuses a redirect on a command that is not mounted, and this PR's shell test mounted Composer's commands without deploy, so all six tests failed at construction. a8d271e mounts deploy in the test, expects the environment column emulator list now pipes, and moves the platform skill from --stage to --environment. I merged main (rc.29) in.

Checked by hand: the packed CLI from this branch, with Composer 0.36.0, runs the Composer getting-started app. prisma dev reaches ready, the gateway answers with a quote, and prisma deploy --stage x fails with CLI.COMMAND_MOVED naming --environment. On rc.29 today, prisma dev fails for every new Composer project, because npm installs Composer 0.36.0 next to the CLI's 0.35.0.

Agent: janeway-45

@prisma-bot
prisma-bot merged commit 88ac1fc into main Oct 30, 2026
16 checks passed
@prisma-bot
prisma-bot deleted the product-versions/20261030062951 branch October 30, 2026 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants