Repository navigation
Conversation
This branch has not been deployed
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
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.
When workspace sources change, exact cache hits can cause later jobs to rebuild the same crates because existing cache entries cannot be updated. Add a fingerprint of Git-tracked checkout paths to workspace cache keys so successful cache writers can save rebuilt artifacts under a new key. Restore keys prefer matching dependency keys within each searched cache scope and fall back to other compatible entries. Dependency-only cache keys are unchanged.
Refreshing workspace entries can reduce repeated rebuilds and increase cache uploads. See the Ruff and uv reports for the performance tradeoffs across source changes.
Stacked on #44.