Release v0.2.4 for Bazel Central Registry.

[PiotrSikora]

No description provided.

[PiotrSikora]

I've decided to tag v0.2.4-bazel off branch, since there are no code changes in the SDK since v0.2.4, so that we can push this as a official v0.2.4 release to BCR.

Let me know if that works, or if you prefer to wait until we release v0.2.5.

cc @mmorel-35 @phlax

[PiotrSikora]

Please ignore the outdated check, since it's only for a dependency update in one of the examples, and we don't need (or want, really, since it would diverge from tagged v0.2.4 release) to fix it before merging this.

[phlax]

fine from Envoy pov - main is still on workspace, and im using a registry hosted in the toolshed repo atm - ill test the bcr version as soon as i get chance

[mmorel-35]

@phlax ,
I saw bazelbuild/bazel-central-registry#7229

You've use dashed while there are underscore in the module name.

That's what I initially provided but @PiotrSikora preferred underscores if I remember correctly

[PiotrSikora]

That's what I initially provided but @PiotrSikora preferred underscores if I remember correctly

AFAICT, you provided underscores from the first commit in #333.

And no, that's definitely not my preference...

But it matches the underscored name is our in WORKSPACE file, which uses dashes, because as far as I recall, you couldn't use dashes in the workspace names (at least not originally...), but it seems that restriction doesn't apply to Bazel modules, so perhaps we should use dashes again?

Note that if you look at the @load statements in .bzl files (here and in Envoy), then you'll notice that all external workspaces are using underscores instead of dashes in their names.

[phlax]

i think my preference is towards using kebab-case for mod names - it kinda makes it clearer that they are names

[PiotrSikora]

I've decided to tag v0.2.4-bazel off branch, since there are no code changes in the SDK since v0.2.4, so that we can push this as a official v0.2.4 release to BCR.

Actually, since there are no code changes, let's merge it to main branch, and then revert version back to v0.2.5-dev.