fix(vercel-with-redwood): update expectation to OpenSSL 3.x engine #4697
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.
Example failure
https://github.com/prisma/ecosystem-tests/actions/runs/8340793087
https://vercel.com/prisma-orm/e2e-vercel-with-redwood/settings shows that the Node.js version is 18.x
It used to pass until
5.12.0-dev.14
(4 days ago)Logs https://github.com/prisma/ecosystem-tests/actions/runs/8298730372/job/22712899025#step:8:329
And now fails since
5.12.0-dev.15
(yesterday)Logs: https://github.com/prisma/ecosystem-tests/actions/runs/8324738211/job/22777110892#step:8:341
So this shows that the runtime changed, we didn't change anything in the logic on our side.