io_bazel_rules_closure@1.0.0

[pcj]

Release: https://github.com/stackb/rules_closure/releases/tag/v1.0.0

Note: this is a variant / fork of https://registry.bazel.build/modules/rules_closure. That one has been stripped down of capabilities and exists mostly to serve j2cl. This one adds back the closure library, restores support for closure-templates and protobuf-javascript. As a homage to the original version I named this one io_bazel_rules_closure.

Automated by Publish to BCR

[bazel-io]

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (io_bazel_rules_closure) 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 io_bazel_rules_closure module at version 1.0.0. The overall structure adheres to the Bazel Central Registry (BCR) policies. However, there is a critical issue in MODULE.bazel regarding the use of use_repo_rule that will prevent this module from being used as a dependency. Please see the detailed comment below.

[fmeum]

Are these debs prod.dependencies? I'm asking since there is a steady volume of security issues found in these libraries and having them enter your build as an http_file dep of a ruleset would be unexpected at least for me.

Are there BCR versions of these libs that you could depend on instead?

[fmeum]

Looking into the future, wouldn't stackb_rules_closure be a more meaningful name?

[meteorcloudy]

+1 for stackb_rules_closure