fix: run the npx fallback from @prisma/composer-cli and default to 0.7.0 - #6
Merged
kristof-siket merged 2 commits intoAug 18, 2026
Merged
Conversation
From 0.7.0 the prisma-composer bin moved from @prisma/composer into the separate @prisma/composer-cli package. The old fallback command fetched @prisma/composer, which no longer contains the bin, so npx would 404. Also updates the default version from 0.6.0 to 0.7.0 and makes the startup log honest: the composer label now prints after the local-bin check, so it reports "composer=local bin" when the repo's own install provides the bin and "composer=<version> (npx fallback)" only when npx actually runs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
kristof-siket
marked this pull request as ready for review
August 18, 2026 08:24
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
1 participant
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.
Problems
1. Wrong package in the npx fallback
When a repo has no local
node_modules/.bin/prisma-composer, the action falls back tonpx --package=@prisma/composer@<version> prisma-composer. From 0.7.0 theprisma-composerbin moved out of@prisma/composerinto a new dedicated package,@prisma/composer-cli. Fetching@prisma/composer@0.7.0via npx finds the package but not the bin, so the fallback command fails for any 0.7.0+ version.The fix changes the fallback to
--package=@prisma/composer-cli@<version>.2. Stale default version
The
composer-versioninput defaulted to0.6.0. Setup PRs generated by the platform now pin^0.7.0and add@prisma/composer-clias an explicit devDependency, so the local bin is present and the fallback does not run for those repos. The default matters for hand-written workflows or repos that omit the devDependency. Updated to0.7.0.3. Misleading startup log
The startup log printed
composer=<version>regardless of whether the local bin or the npx fallback ran. In a real 0.7.0 run with a local bin the log would saycomposer=0.6.0(the old default), which is wrong on both counts.The fix moves the composer label to after the local-bin check: it now prints
composer=local binwhen the repo's own install provides the bin, andcomposer=<version> (npx fallback)only when npx actually runs.Scope note
Today's generated setup PRs ship
@prisma/composer-clias a devDependency, so the local bin is always present for repos connected through the Console. The fallback only matters for hand-written workflows or repos without that devDependency.Changes
main.mjs: default"0.6.0"→"0.7.0"; fallback package@prisma/composer→@prisma/composer-cli; log label moved and made path-awareaction.yml: default and description updated to matchREADME.md: table default updated to0.7.0; Node 22 limitation de-versioned; inline YAML comment about the 0.6.0 crash removed