Repository navigation
Follow the products' released versions: @prisma/composer-cli 0.36.0 -> 0.37.0; @prisma/composer 0.36.0 -> 0.37.0 - #385
Merged
Conversation
…> 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
enabled auto-merge (squash)
November 6, 2026 15:55
commit: |
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>
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.
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
devversion of the CLI; the conformance checks on this pull request are what stand between a product release and that dev build.