chore: pin zbuild to release commit and drop zbuild.zon refs

README.md

@@ -676,7 +676,7 @@ GitHub releases are managed with release-please:
 
 1. Conventional commits merged to `main` update or create the release PR.
 2. Merging that PR tags a new GitHub release and bumps `package.json`.
-3. `build.zig.zon` and `zbuild.zon` are kept in sync from the same release-please version.
+3. `build.zig.zon` is kept in sync from the same release-please version.
 4. The release workflow installs dependencies, runs `pnpm build:js`, and publishes the root package directly with `npm publish` via npm trusted publishing.
 5. No `NPM_TOKEN` secret is required for npm publish; GitHub Actions OIDC (`id-token: write`) is used together with `--provenance`.
 6. The published npm package is the JS distribution only (`lib/` and `ts/`).

build.zig.zon

@@ -6,8 +6,8 @@
     .paths = .{ "build.zig", "build.zig.zon", "src", "include" },
     .dependencies = .{
         .zbuild = .{
-            .url = "git+https://github.com/ChainSafe/zbuild?ref=refactor/comptime-library-rewrite#7ec852f1c6495b62d964e311bd210b6f9a3015be",
-            .hash = "zbuild-0.4.0-XJFav9lXAgCtcFwxSb5qEkex3kijECLtqo7z9FzrkUaf",
+            .url = "git+https://github.com/chainsafe/zbuild.git#f7d5f19de09f2808e54acf599605f9e18c9bd804",
+            .hash = "zbuild-0.4.0-XJFav-1nAgDmfVY1nVSIIzbkcbuHZj7yMb7Fv8yvznPO",
         },
     },
     .options_modules = .{

release-please-config.json

@@ -8,10 +8,6 @@
         {
           "path": "build.zig.zon",
           "type": "generic"
-        },
-        {
-          "path": "zbuild.zon",
-          "type": "generic"
         }
       ]
     }