fix(build): location-independent theme signature - #48
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 theme template signature hashed absolute file paths. CI Python toolcache updates move the package dir between runs → same templates, different signature → full cache invalidation every run, so the build cache was never reused.
Now hashes template contents with paths relative to each theme directory: identical templates always yield the same signature, wherever installed. Includes a unit test proving two dirs at different absolute paths with identical content produce equal signatures.
Depends on #47 (content-based theme signature); follows the tikz hash cache as part of making the build cache CI-friendly.