Skip to content

chore: work around bugs using cache_content_hash#12124

Merged
ludamad merged 2 commits intomasterfrom
ad/cache-content-hash
Feb 19, 2025
Merged

chore: work around bugs using cache_content_hash#12124
ludamad merged 2 commits intomasterfrom
ad/cache-content-hash

Conversation

@ludamad
Copy link
Collaborator

@ludamad ludamad commented Feb 19, 2025

No description provided.

@ludamad ludamad requested a review from charlielye as a code owner February 19, 2025 22:29
@ludamad ludamad enabled auto-merge (squash) February 19, 2025 22:30
@ludamad ludamad merged commit ef79f9d into master Feb 19, 2025
8 checks passed
@ludamad ludamad deleted the ad/cache-content-hash branch February 19, 2025 22:34
ludamad pushed a commit that referenced this pull request Feb 19, 2025
…12125)

Running `yarn install` will format the package.json for all packages in
the workspace. This will cause `cache_content_hash` to fail on CI due to
changed files, which (before #12124) caused the build to terminate
abruptly (see
[here](https://github.com/AztecProtocol/aztec-packages/actions/runs/13422411604/job/37497960586?pr=12096#step:7:109)
for an example).

This PR adds all package.json files to yarn's `immutablePatterns`, so if
it detects that the install process changed them it, it will fail with
`The checksum for **/package.json has been modified by this install,
which is explicitly forbidden.` and a nice exit code, which should be
visible on the CI run. This only applies to CI runs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants