fix(nix): refresh stale npmDepsHash for hermes-tui - #17585
Closed
alt-glitch wants to merge 1 commit into
Closed
Conversation
Collaborator
Author
|
No longer needed — the auto-fix workflow pushed the hash correction directly after adding the GitHub App to the ruleset bypass list. |
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.
The
npmDepsHashinnix/tui.nixwent stale after #17175 merged with an updatedui-tui/package-lock.json.The auto-fix workflow (#16285) triggered but cannot push to main due to branch protection rules (
GH013: Changes must be made through a pull request). The GitHub App token isn't exempted from the ruleset — so the auto-fix mechanism is currently non-functional regardless of trigger timing.This PR manually applies the correct hash from the nix build error:
Note: The auto-fix workflow from #16285 needs its GitHub App added to the branch protection bypass list, otherwise it will keep failing on every future hash drift.