We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Turborepo
We discovered this while updating from Node.js v18 to v20.
I was surprised to see that tests were passing when I explicitly expected them to fail because of an update.
There are real issues of using Turbo cache in CI if it does not consider the Node.js version.
Include Node.js version into the hash key.
N/A
The text was updated successfully, but these errors were encountered:
Duplicate of #4124
Sorry, something went wrong.
No branches or pull requests
Which project is this feature idea for?
Turborepo
Describe the feature you'd like to request
We discovered this while updating from Node.js v18 to v20.
I was surprised to see that tests were passing when I explicitly expected them to fail because of an update.
There are real issues of using Turbo cache in CI if it does not consider the Node.js version.
Describe the solution you'd like
Include Node.js version into the hash key.
Describe alternatives you've considered
N/A
The text was updated successfully, but these errors were encountered: