I've now reviewed the complete diff. This is a straightforward automated dependency update PR. Let me verify my understanding of the changes:

Summary of changes:

1. GitHub workflows: opencode version bump 1.3.8 -> 1.4.3
2. Bazel build deps (build_deps.MODULE.bazel): minor bumps to apple_support, aspect_rules_ts, rules_nodejs, and wasm-tools (1.245.1 -> 1.246.2)
3. Bazel deps (deps.MODULE.bazel): bumps to brotli, capnp-cpp, dragonbox, fp16, highway, nbytes (0.1.3 -> 0.1.4), workerd-cxx
4. Rust crates (~50 files): all patch/minor version bumps to standard dependencies — capnp, cc, fastrand, hashbrown (new 0.17.0 for indexmap), icu_* (2.1.x -> 2.2.0), indexmap, js-sys, libc, litemap, semver, tokio, wasm-bindgen, zerovec, etc.

All changes are:

• Auto-generated by the crate_universe tool / dependency update automation
• Patch or minor semver bumps (no major version changes)
• Version strings, sha256 hashes, and Bazel label references updated consistently
• No source code changes, no API changes, no behavioral changes
• No .capnp schema changes, no compat flag changes, no security-sensitive modifications

The new hashbrown-0.17.0 BUILD file is properly structured and required by the indexmap 2.14.0 upgrade.

There are no actionable issues — no logic bugs, security concerns, backward compatibility violations, or incorrect wiring in the build files.

LGTM

github run

The generated output of @cloudflare/workers-types matches the snapshot in types/generated-snapshot 🎉

Looks like builds fail since the updated version of highway starts using cc_test without importing it which is not supported with Bazel 9. We could either patch highway (too much effort) or simply add cc_test to the existing list we have with --incompatible_autoload_externally (not pretty but much easier).