-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
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
feat: factor engines into global cache key #8173
feat: factor engines into global cache key #8173
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
5 Ignored Deployments
|
c1cf131
to
5d05506
Compare
🟢 Turbopack Benchmark CI successful 🟢Thanks |
🟢 CI successful 🟢Thanks |
74fcf2d
to
0f08755
Compare
5d05506
to
31952ca
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of the root package.json is in the global cache inputs though, right? Is this double-including it?
83eb77b
to
28643f5
Compare
42d43b4
to
e468cb1
Compare
No, we don't include the file hash of the root |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you rebase this so I can see the diff again? The explanation makes sense, I was thinking of aa019da, but that was for package-specific package.json
s that we try to always include.
75abd54
to
4072884
Compare
31952ca
to
986d423
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some merge conflicts, but looks good otherwise!
@@ -407,14 +426,15 @@ mod test { | |||
global_file_hash_map: &global_file_hash_map, | |||
root_external_dependencies_hash: Some("0000000000000000"), | |||
root_internal_dependencies_hash: Some("0000000000000001"), | |||
engines: Default::default(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's the default?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{}
turborepo-tests/integration/tests/run/single-package/with-deps-run.t
Outdated
Show resolved
Hide resolved
turborepo-tests/integration/tests/run/single-package/with-deps-run.t
Outdated
Show resolved
Hide resolved
turborepo-tests/integration/tests/run/single-package/with-deps-run.t
Outdated
Show resolved
Hide resolved
### Description Changing the `engines` field in the root `package.json` can affect the execution of tasks so it should affect the global cache. This PR adds the `engines` struct to the global cache key. ### Testing Instructions Added new integration test verifying that changing `engines` results in a cache miss.
### Description Changing the `engines` field in the root `package.json` can affect the execution of tasks so it should affect the global cache. This PR adds the `engines` struct to the global cache key. ### Testing Instructions Added new integration test verifying that changing `engines` results in a cache miss.
Description
Changing the
engines
field in the rootpackage.json
can affect the execution of tasks so it should affect the global cache.This PR adds the
engines
struct to the global cache key.Testing Instructions
Added new integration test verifying that changing
engines
results in a cache miss.