Skip to content
4 changes: 2 additions & 2 deletions build.zig.zon
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,8 @@
},
},
.hashtree = .{
.url = "git+https://github.com/ChainSafe/hashtree-z.git#81b7303f72e202e966f71eedf4be1d8d33e2fcaa",
.hash = "hashtree-0.1.0-sBOoviYWAAA1HcTLhxWt0TtrLFXvYM5gOvxpu_Rreiiw",
.url = "git+https://github.com/ChainSafe/hashtree-z.git#f5c1b81da167f84376fb94aef29a57fc6c08dc28",
.hash = "hashtree-0.1.0-sBOovj8WAAAGCN62cybnffy7b4ITTQsog2oOG2AQZl9L",
},
.snappy = .{
.url = "git+https://github.com/ChainSafe/snappy.zig#713942410426051da6107a955b29f3f152815622",
Expand Down
1 change: 1 addition & 0 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,7 @@
"targets": [
"aarch64-apple-darwin",
"aarch64-unknown-linux-gnu",
"aarch64-unknown-linux-musl",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Update ZAPI before adding the ARM64 musl target

Adding this entry makes the publish workflow parse zapi.targets with the declared @chainsafe/zapi dependency (pnpm zapi build-artifacts in .github/workflows/publish-bindings.yml), but package.json/pnpm-lock.yaml still pin @chainsafe/zapi to 2.0.0. That version's config parser only accepts its built-in target list, which does not include aarch64-unknown-linux-musl, so the release job will fail with Unsupported target before it can publish any bindings; runtime loading also keeps using the old requireNapiLibrary mapping. Please bump @chainsafe/zapi and the lockfile to the release containing ChainSafe/zapi#47 in the same change.

Useful? React with 👍 / 👎.

"x86_64-apple-darwin",
"x86_64-unknown-linux-gnu",
"x86_64-unknown-linux-musl"
Expand Down
Loading