Closed tpudlik closed 5 days ago
I'm not too familiar with Bazel modules. Will this change affect anyone users of Emboss that are using Bazel? I suspect not, since this seems to just affect the equivalent of WORKSPACE (?), but I would want to confirm that.
That's right, existing Bazel projects that pull in Emboss through their WORKSPACE will not be affected.
Any blockers to merging this?
This will also make it easier to maintain emboss in the BCR (https://github.com/bazelbuild/bazel-central-registry/tree/main/modules/emboss).
Ideally we'd also set the
version
field ofmodule
, but the version value is unknown until the release workflow actually runs (because it encodes the release timestamp). In practice we should probably change the versioning scheme to pull the version number fromMODULE.bazel
, but I imagine that requires some discussion.