-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pnpm: 9.12.1 -> 9.12.2 #349093
pnpm: 9.12.1 -> 9.12.2 #349093
Conversation
Most packages fail with Result of 42 packages failed to build:
2 packages built:
|
Looks like upstream changed their store format, which broke most of our FOD hashes :/ |
Running a diff for example on the old and new
I'll update all the pnpm hashes soon. |
|
podman-desktop from #343648 needs to be updated |
|
Updated podman-desktop and metacubexd hashes |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. We should notify open PRs about this change so that they can update their hashes.
I'll do that after this is merged, also they should get a merge conflict for the hashes too. |
Thanks for notifying them about the hash changes! I also checked which PR got broken by this and found the same ones as you did, except for Edit: nevermind, |
The latest release of pnpm (9.12.2) includes a fix that changes the output hash of dependencies - NixOS/nixpkgs#349093 - pnpm/pnpm#8625
Is this hash change unavoidable? This type of behavior should be kept to a minimum. |
This is why |
Alternatively, can we ask upstream to commit to not breaking the hashes outside of major version bumps? And write a CI test for upstream that ensures this? |
But is it possible for us to at least "fixup" them to something simpler, so it doesn't matter? Or is this completely happening in upstream servers and we don't have any control of it? |
If we had renamed these files back to what pnpm < 9.12.2 used, the configure hook would fail installing dependencies as pnpm 9.12.2 wouldn't find the expected files in its store. Maybe we could have fixed them up and then unfixed them during configuration. But I think that wouldn't be very maintainable in the long run.
I think this is a good way to go. If upstream agrees that a change to the store is a breaking change, they might just bump to a new major version every time the store format changes. In those cases, we can just release a new |
I created an issue upstream to discuss this: pnpm/pnpm#8713 |
One more thing: we may need a release note for this, as it's somehow breaking. |
Until we don't have that many pnpm packages (currently there are about 50), mass hash changes are not the end of the world if it only happens 1 or 2 times in a year. Package update PRs that use Hovewer package init PRs won't get merge conflicts and we need to hunt these down and notify the author, this is where we could've done better. Searching for
Exactly, this should've been only released in the next major version.
Mostly for people using |
Release: https://github.com/pnpm/pnpm/releases/tag/v9.12.2
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.