You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6c41548
Browse filesBrowse the repository at this point in the historyBrowse files
The host runs Composer 0.26.0: one config file, no prisma-composer binary (8.0.0-rc.20) (#330)
Slice 3 of the one-config-file project
([prisma/orm#30536](prisma/orm#30536)). Composer
0.26.0 published the merged config
([prisma/composer#328](prisma/composer#328)) and
dropped the `prisma-composer` binary
([prisma/composer#331](prisma/composer#331));
this PR makes the host carry it. Merging publishes `prisma@8.0.0-rc.20`.
From a Composer project outside any workspace, with this branch's
`prisma` and Composer 0.26.0 from the registry:
```
$ prisma dev module.ts # with prisma-composer.config.ts left beside prisma.config.ts
CLI.CONFIG_SECTION_INVALID The 'composer' section of .../prisma.config.ts is invalid.
CONFIG.FILE_RETIRED .../prisma-composer.config.ts is no longer read. Composer reads its
configuration only from the `composer` section of prisma.config.ts. ...
$ prisma --version
8.0.0-rc.20
```
## The decision
`@prisma/cli` and `prisma` pin `@prisma/composer-cli` and
`@prisma/composer` at 0.26.0 and the version advances to 8.0.0-rc.20, so
`prisma@latest` runs Composer's family with the `composer` section of
`prisma.config.ts` as its configuration. The automatic pin-bump workflow
did not fire (Composer's publish could not notify this repository), so
this PR carries the bump.
## What the bump changes in the host
- **Tests.** The config fixture that held `composer: { configPath }` now
proves the retirement: `dev --config` against it fails with the engine's
`CLI.CONFIG_SECTION_INVALID` headline and Composer's
`CONFIG.FIELD_RETIRED` diagnostic, exit 2, on every platform, since
validation now fails before the handler runs. A second fixture holds a
valid section built with `defineConfig as composer` from
`@prisma/composer/config` and proves the handler runs against it.
- **Conformance.** The composer-cli engine-pin exception in
`scripts/conformance.ts` is removed, as its own note said this bump
would do. The suite reports nothing.
- **The shipped skill.** `skills/prisma-platform-core-concepts/SKILL.md`
no longer says `prisma-composer.config.ts` is mandatory or that `dev`
fails with `CONFIG.FILE_MISSING`. It describes the `composer` section
and the three retirement codes in the same terms as Composer's own
skill, with the fix for each.
- **Isolation.** `composer-isolation.test.ts` passes unchanged: mounting
the 0.26.0 family still loads neither Alchemy nor `effect` on an
unrelated command.
## Verification
- Build, typecheck, lint, cli tests (1027), cli-engine tests (1025),
`test:scripts`, `check:skill-packaging`, `manifest-pins`,
`composer-isolation`, and `check:conformance` with zero failing and zero
allowed.
- Manual QA against the published 0.26.0 in a project outside the
workspace, recorded in the project folder: `--version`, `deploy --help`,
`dev --help` exit 0 and list neither `destroy` nor `log`; the retired
file gives `CONFIG.FILE_RETIRED`; the retired field gives
`CONFIG.FIELD_RETIRED`; an `effect` forced to 4.0.0-rc.118 gives
`CLI.CONFIG_UNREADABLE` naming the missing module while `--version`
still exits 0.
- `prisma dev` to ready still needs `alchemy` as a direct dependency in
a plain pnpm project; that is a Composer defect fixed in
[prisma/composer#332](prisma/composer#332), not
a host matter, and will ship in Composer's next release.
## Not in this PR
- New commands. `destroy` and `log` remain operations on
`@prisma/composer/control`; their command-line form is a separate
grammar project.
- The prisma/web pages, which land in their own PR after this release is
on `latest`.
Agent: columbo-17
🤖 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 Fable 5.1 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: packages/cli-conformance/package.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
{
2
2
"name": "@repo/cli-conformance",
3
3
"private": true,
4
-
"version": "8.0.0-rc.19",
4
+
"version": "8.0.0-rc.20",
5
5
"description": "Reusable conformance checks for the engine's consumers: import purity over built output, config-section validators that never throw, and verification of the tarballs a registry would receive. Depends on no package it checks.",
0 commit comments