Re:ZA̡͊͠͝LGΌ causes "Invalid MD5 checksum on messages"
by mdaniel on Saturday May 08, 2021 @07:06PM
(#27091625)
Strictly speaking "[email protected]" was already present, drug in transitively by something else, that's why the yarn.lock folded the older version into the existing checksum
I came very close to commenting on the PR, but since it was pointed out elsewhere that the fix was to the wrong file, I suspected it was going to be closed wontfix anyway
I came very close to commenting on the PR, but since it was pointed out elsewhere that the fix was to the wrong file, I suspected it was going to be closed wontfix anyway