Add envoy-examples and envoy-example-wasm-cc bzlmod modules v0.2.0.envoy

[Copilot]

Adds bzlmod registry entries for the envoyproxy/examples repository v0.2.0 release.

Modules Added

envoy-examples (bazel-registry/modules/envoy-examples/0.2.0.envoy/)

• Root module for examples repository
• Dependencies: envoy-example-wasm-cc, rules_go, rules_pkg, rules_python, rules_shell
• Strip prefix: examples-0.2.0

envoy-example-wasm-cc (bazel-registry/modules/envoy-example-wasm-cc/0.2.0.envoy/)

• WASM-C++ examples submodule
• Dependencies: emsdk, envoy (1.36.4-dev), envoy_api, envoy_build_config, envoy_mobile, envoy_toolshed, grpc, rules_cc, rules_fuzzing, rules_go, rules_perl, rules_proto_grpc, rules_pkg, rules_python, rules_rust, toolchains_llvm (dev)
• Strip prefix: examples-0.2.0/wasm-cc

Both modules reference the same source tarball (https://github.com/envoyproxy/examples/archive/refs/tags/v0.2.0.tar.gz, SHA256: SiuPa8NFGBYDZvgXETTh1wiHvZjQGwayNQKUhrj8FhE=) with different strip_prefix values to extract appropriate subdirectories.

Development overrides (local_path_override, git_override) from upstream MODULE.bazel files are excluded per registry conventions.

Original prompt

Summary

Add two new bzlmod modules to the bazel-registry/modules/ directory for the envoyproxy/examples repository.

Modules to Add

1. envoy-examples module

Create bazel-registry/modules/envoy-examples/ with:

metadata.json:

{
  "homepage": "https://github.com/envoyproxy/examples",
  "maintainers": [],
  "repository": [
    "github:envoyproxy/examples"
  ],
  "versions": [
    "0.2.0.envoy"
  ],
  "yanked_versions": {}
}

0.2.0.envoy/MODULE.bazel:

module(
    name = "envoy-examples",
    version = "0.2.0.envoy",
)

bazel_dep(name = "envoy-example-wasm-cc", version = "0.2.0.envoy")
bazel_dep(name = "rules_go", version = "0.59.0", repo_name = "io_bazel_rules_go")
bazel_dep(name = "rules_pkg", version = "1.1.0")
bazel_dep(name = "rules_python", version = "1.7.0")
bazel_dep(name = "rules_shell", version = "0.6.1")

0.2.0.envoy/source.json:

{
  "url": "https://github.com/envoyproxy/examples/archive/refs/tags/v0.2.0.tar.gz",
  "integrity": "sha256-<COMPUTE_HASH>",
  "strip_prefix": "examples-0.2.0"
}

Note: The local_path_override from the source MODULE.bazel should NOT be included in the registry version - users of the registry module will get envoy-example-wasm-cc from the registry instead.

2. envoy-example-wasm-cc module

Create bazel-registry/modules/envoy-example-wasm-cc/ with:

metadata.json:

{
  "homepage": "https://github.com/envoyproxy/examples",
  "maintainers": [],
  "repository": [
    "github:envoyproxy/examples"
  ],
  "versions": [
    "0.2.0.envoy"
  ],
  "yanked_versions": {}
}

0.2.0.envoy/MODULE.bazel:

module(
    name = "envoy-example-wasm-cc",
    version = "0.2.0.envoy",
)

bazel_dep(name = "emsdk", version = "4.0.13")
bazel_dep(name = "envoy", version = "1.36.4-dev")
bazel_dep(name = "envoy_api", version = "1.36.4-dev")
bazel_dep(name = "envoy_build_config", version = "1.36.4-dev")
bazel_dep(name = "envoy_mobile", version = "1.36.4-dev")
bazel_dep(name = "envoy_toolshed", version = "0.3.25")
bazel_dep(name = "grpc", version = "1.72.0", repo_name = "com_github_grpc_grpc")
bazel_dep(name = "rules_cc", version = "0.1.1")
bazel_dep(name = "rules_fuzzing", version = "0.6.0")
bazel_dep(name = "rules_go", version = "0.59.0", repo_name = "io_bazel_rules_go")
bazel_dep(name = "rules_perl", version = "0.4.1")
bazel_dep(name = "rules_proto_grpc", version = "5.0.0")
bazel_dep(name = "rules_pkg", version = "1.1.0")
bazel_dep(name = "rules_python", version = "1.7.0")
bazel_dep(name = "rules_rust", version = "0.68.1")

bazel_dep(name = "toolchains_llvm", version = "1.4.0", dev_dependency = True)

IMPORTANT: The git_override blocks from the source wasm-cc/MODULE.bazel should NOT be included in the registry version. Those are development overrides - the registry version should rely on the dependencies being available from the registry (BCR or this toolshed registry).

0.2.0.envoy/source.json:

{
  "url": "https://github.com/envoyproxy/examples/archive/refs/tags/v0.2.0.tar.gz",
  "integrity": "sha256-<COMPUTE_HASH>",
  "strip_prefix": "examples-0.2.0/wasm-cc"
}

Notes

1. The integrity hash needs to be computed by downloading the tarball from https://github.com/envoyproxy/examples/archive/refs/tags/v0.2.0.tar.gz and computing its SHA256 in SRI format.

2. Both modules point to the same source tarball but with different strip_prefix values to extract the appropriate subdirectory.

3. Follow the existing patterns in the toolshed bazel-registry for file formatting and structure (see examples like cel-cpp, emsdk, etc.).

4. The version suffix .envoy is required per toolshed conventions.

This pull request was created from Copilot chat.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[netlify]

✅ Deploy Preview for nifty-bassi-e26446 ready!

Name	Link
🔨 Latest commit	f290197
🔍 Latest deploy log	https://app.netlify.com/projects/nifty-bassi-e26446/deploys/6984927e36caba0008799251
😎 Deploy Preview	https://deploy-preview-3705--nifty-bassi-e26446.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.