ci(nix): refresh frontend npm dependency hash - #1
Merged
Conversation
Use Nix's fake hash only on the temporary probe branch so GitHub Actions reports the updated fixed-output hash without changing main.
Use the dependency hash reported by Nix for the shared frontend lockfile in both frontend packages.
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.
What
Temporarily replace the two frontend workspace npm dependency hashes with
lib.fakeHash.Why
The root package lock gained Day.js, so the existing Nix fixed-output hash is stale. This draft PR exists only to let the Pull Request Checks workflow report the new hash without pushing a deliberately failing probe to
main.Validation
git diff --checkgot: sha256-...