jsinterop_generator@20250630

[publish-to-bcr-bot]

Release: https://github.com/google/jsinterop-generator/releases/tag/v20250630

Automated by Publish to BCR

[bazel-io]

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (jsinterop_generator) 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.

[mollyibot]

@bazel-io skip_check incompatible_flags

[meteorcloudy]

Should we switch to the BCR version? archive_override won't work transitively

[mollyibot]

I initially switched to stable bcr version, but my team suggests we want to test with the latest MASTER change.

[Wyverald]

if you do this, I'd caution against using bcr_test_module with module_path: '.'. You'd be doing running the BCR compatibility test with an override, which is certainly not what the BCR automation ought to be doing. It's fine for you to test compatibility with tip-of-tree master in your own CI (so leaving the overrides in is okay), but maybe not on BCR.

[meteorcloudy]

Exactly, you have to make sure what you check into BCR is actually usable by other people, with the current MODULE.bazel, j2cl will be missing when this module is used via a bazel_dep, if you add a anonymous-module-test test, you'll probably catch this.