[email protected]

[publish-to-bcr-bot]

Release: https://github.com/vimana-cloud/rules_wasm/releases/tag/v1.0.15

Automated by Publish to BCR

[bazel-io]

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (rules_wasm) have been updated in this PR. Please review the changes.

[ouillie]

Going to try fixing the glibc compatibility issues upstream.

Regarding the Bazel 6.x failures, I'm a bit confused about the need for a WORKSPACE file for something that's being distributed via the BCR. Is there any documentation on what Bazel expects to find in the WORKSPACE file? I tried reproducing locally like this:

docker run -it gcr.io/bazel-public/ubuntu2004
git clone https://github.com/vimana-cloud/rules_wasm.git
cd rules_wasm/example
USE_BAZEL_VERSION=6.5.0 bazel test //...

But it just said:

Unable to find package for @rules_wasm//:wasm.bzl: The repository '@rules_wasm' could not be resolved: Repository '@rules_wasm' is not defined.

I'm assuming there's some sort of shim I'm missing? I noticed on BuildKite it refers to the repository as //:rules_wasm~override but there's a lot going on and it's kinda hard to tell what the ~override means.

[meteorcloudy]

@ouillie With Bazel 6, Bzlmod was not enabled by default and a WORKSPACE file is still required to identify to repo root.

To reproduce the error, you'll need to add --enable_workspace to the build command.

It's also fine if you want to drop Bazel 6 support.