Repository navigation
chore: update nix node_modules hashes - #59728
Conversation
![opencodejr[bot]](https://avatars.githubusercontent.com/in/5497873?s=60&v=4){kind=small}
There was a problem hiding this comment.
This is an automated refresh of the Nix node_modules hashes. Only nix/hashes.json changes, which matches the bot's stated scope. The hashes were computed for d76552c, which is the current head of dev and follows the recent dependency removals (#59713, #59714, #59716), so an update is expected. I couldn't confirm the new values because Nix isn't available in the review environment. The Nix CI build is what checks them. Public API: unchanged.
1e07734 to
51eeb8a
Compare
There was a problem hiding this comment.
No earlier points were left open. The bot recomputed the hashes after #59712 (removal of unused root dependencies) landed on dev. The diff against dev is still only nix/hashes.json, and that change is needed because the root dependencies changed. I couldn't confirm the new values because Nix isn't available here. The Nix CI build is what checks them. Public API: unchanged.
51eeb8a to
3ac66f2
Compare
There was a problem hiding this comment.
No earlier points were left open. The bot recomputed the hashes after the recent lockfile refreshes (#59737–#59746) landed on dev. The diff against dev is still only nix/hashes.json, and the one later dev commit (#59695) doesn't change bun.lock. I couldn't confirm the new values because Nix isn't available here. The Nix CI build is what checks them. Public API: unchanged.
3ac66f2 to
72ac72d
Compare
Updates
nix/hashes.jsonto the node_modules hashes computed for d76552c by bot-nix-hashes. check-bot-scope keeps this branch to that file.