Add proxy-wasm-cpp-sdk@0.0.0-20260123-894dd29

[mmorel-35]

Adds proxy-wasm-cpp-sdk module based on commit 894dd29 (2026-01-23), newer than existing PR's e5256b0 (2025-09-25).

Module Configuration

• Version: 0.0.0-20260123-894dd29 (8-digit date format)
• Source: https://github.com/proxy-wasm/proxy-wasm-cpp-sdk/archive/894dd29ff8333d6cc51b416d334568058d6aef71.tar.gz
• Maintainers: PiotrSikora, martijneken, mpwarres, leonm1, phlax
• Dependencies: emsdk 4.0.13, protobuf 29.3, re2, rules_cc 0.2.0, rules_python 1.4.1
• CI matrix: Bazel 7.x, 8.x on debian11, macos, ubuntu2204

Patches

1. proxy-wasm-cpp-sdk.patch - Comments out emscripten ALLOW_MEMORY_GROWTH and INITIAL_HEAP flags (from envoyproxy/toolshed)
2. module_version.patch - Updates MODULE.bazel version string from 0.0.0 to 0.0.0-20260123-894dd29

Notes

Upstream removed rules_proto dependency between commits e5256b0 and 894dd29.

@bazel-io skip_check unstable_url

[bazel-io]

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (proxy-wasm-cpp-sdk) have been updated in this PR.
Please review the changes. You can view a diff against the previous version in the "Generate module diff" check.

[gemini-code-assist]

Code Review

This pull request adds the proxy-wasm-cpp-sdk module at version 0.0.0-20260123-894dd29. The submission is well-structured and largely adheres to the Bazel Central Registry guidelines. However, I've identified a critical issue in the presubmit.yml configuration concerning how build targets are referenced. This needs to be corrected to ensure the presubmit checks can pass. Since this is a new module, a review of the metadata.json by @bazelbuild/bcr-maintainers is also advisable as per the contribution guidelines.

[mmorel-35]

@bazel-io skip_check unstable_url

[meteorcloudy]

Adds proxy-wasm-cpp-sdk module based on commit 894dd29 (2026-01-23), newer than existing PR's e5256b0 (2025-09-25). Merges maintainer lists from both efforts.

Which modules are you merging?

[mmorel-35]

No modules are merged here, just the list of maintainers between this pr and the one from #7228

[mmorel-35]

@bazel-io skip_check incompatible_flags

[mmorel-35]

@meteorcloudy ,

This needs a patch of emsdk to be bazel 9 compatible