[CI]: Add Prisma resolutions to tutorial-e2e test project #6773
Conversation
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
redwoodjs-bot
bot
added
cherry-pick
release:chore
jtoar
deleted the
cherry-pick-next-4437e21b631119ae406eb5de38ea1f38b0bfcee1
branch
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.
The Prisma v4.5.0 upgrade (#6485) revealed a bug in the tutorial e2e CI job since the
yarn rw g scaffoldcommand now has an install step.The problem is that the tutorial e2e test project uses the current stable version of Redwood (v3.2.1), which has Prisma v4.3.1. When we use rwfw to link, it adds v4.5.0 to the root package.json. Since there's now two different versions of Prisma, after the install step happens in
yarn rw g scaffold, yarn realizes it can't hoist Prisma anymore since there's two versions (or something like that), so it installs v4.3.1 intonode_modules/@redwoodjs/cli/node_modules.