Skip to content

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

Merged
prisma-bot merged 1 commit into
mainfrom
product-versions/20261106155456
Nov 6, 2026
Merged

prisma-bot merged 1 commit into
mainfrom
product-versions/20261106155456

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.36.0 -> 0.37.0; @prisma/composer 0.36.0 -> 0.37.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.37.0; @prisma/composer 0.36.0 -> 0.37.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) November 6, 2026 15:55
@coderabbitai

coderabbitai Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Summary by CodeRabbit

  • Chores
    • Updated supporting components used by the CLI and Prisma packages. No user-facing changes are included.

Walkthrough

The CLI manifest updates @prisma/composer-cli and @prisma/composer from version 0.36.0 to 0.37.0. The Prisma manifest updates @prisma/composer-cli from version 0.36.0 to 0.37.0.

Merge Risk: Minimal · up to 4b7ba

The Composer versions are aligned across both manifests. No actionable merge-blocking risk is identified; merge after normal checks pass.

Pre-merge checks: Passed 5

Check name Status Explanation
Title check Passed The title identifies both dependency version updates.
Description check Passed The description identifies the dependency updates and their release context.
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 0 files. (2 skipped: 2 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
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: e36caa41-2e50-4e84-9e5e-afccbc652628
Commits

Reviewing files that changed from the base of the PR and between 4e52dff and 4b7bae8.

Files ignored due to path filters: 1

  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing: 2

  • packages/cli/package.json
  • packages/prisma/package.json

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

@pkg-pr-new

pkg-pr-new Bot commented Nov 6, 2026

Copy link
Copy Markdown

Open in StackBlitz

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

commit: 4b7bae8

@prisma-bot
prisma-bot merged commit da76c74 into main Nov 6, 2026
16 checks passed
@prisma-bot
prisma-bot deleted the product-versions/20261106155456 branch November 6, 2026 15:58
wmadden pushed a commit that referenced this pull request Nov 6, 2026
Merging this PR publishes `prisma@8.0.0-rc.31` and
`@prisma/cli@8.0.0-rc.31` under `latest`. It is the first release that
carries Composer 0.37.0:

```console
$ npm view prisma@8.0.0-rc.31 dependencies
'@prisma/composer-cli': '0.37.0'
```

The main user benefit of Composer 0.37.0 is a much smaller install: 1.6
GB down to 473 MB.

## What changes

- **Version bump 8.0.0-rc.30 → 8.0.0-rc.31**, made by `pnpm
bump-version` (the `publish-npm-version` skill). The same files change
as in #380. `@prisma/compute` keeps its own version; only its
`workspace:` dependency on `@repo/tsconfig` moves.
- **The Composer pins** moved to 0.37.0 in #385, which prisma-bot opened
and merged. That commit's CI on `main` passed, including the real-API
end-to-end suite.
- **`docs/reference/error-reference.md` gets a `CONFIG` section.**
Composer 0.37.0 adds three codes: `CONFIG.ADAPTER_FAILED`,
`CONFIG.ADAPTER_INVALID` and `CONFIG.SECRET_AS_PLAIN_VALUE`. The page
had no `CONFIG` section at all, so the ten older `CONFIG.*` codes
Composer raises were missing too. The section lists all 13, written from
the 0.37.0 package source. The page says family codes are kept current
by hand when the CLI moves to a new family release, which is why this
rides in the release PR.

## What merging does

The squashed push to `main` changes the root version. The `Publish to
npm` workflow then publishes `@prisma/cli-engine` and `@prisma/cli`, and
creates a GitHub Release with generated notes (marked pre-release on the
RC line). See
[`docs/oss/versioning.md`](../blob/main/docs/oss/versioning.md).

Agent: dumbo-83

🤖 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>
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