Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

node-v14.17.0-macos-x64 hardcoded hash mismatch in 3.2

See original GitHub issue

https://github.com/vercel/pkg-fetch/blob/b30cbad6ea4297dcc28a2024e322971ec7e49c0b/lib/expected.ts#L82 https://github.com/vercel/pkg-fetch/blob/b30cbad6ea4297dcc28a2024e322971ec7e49c0b/lib/expected.ts#L83

$ shasum -a 256 -c node-v14.17.0-macos-x64.sha256sum
node-v14.17.0-macos-x64: OK
$ cat node-v14.17.0-macos-x64.sha256sum
074a517cbf9a5abd2faa976426eeea37fb7a0cf976e4441b757deac2b66beb8a  node-v14.17.0-macos-x64

The hardcoded hash for node-v14.17.0-macos-x64 doesn’t match the binary and also not the sha256 file next to the binary in the 3.2 release, breaking builds.

Issue Analytics

State:
Created 2 years ago
Comments:6 (1 by maintainers)

Top GitHub Comments

2reactions

leerobcommented, Jun 25, 2021

Sure, I can do that.

1reaction

jeseccommented, Jun 24, 2021

@leerob

On second thought, for the sake of correctness, I think we should still publish 3.2.1. Can you publish 3.2.1 to npm when you have time? It is already tagged on Github.