bazel version and compatibility number out of sync

[zaucy]

The current release process doesn't increment the version or compatibility level in the MODULE.bazel file. I've recently submitted EnTT to the BCR and had to patch it in (so no worries there.)

I'm creating this issue for visibility sake, but I plan on creating a PR to fix this myself in the coming weeks.

edit:

bazelbuild/bazel-central-registry#1904 (comment)

The current advice is to avoid compatibility_level altogether so it would probably be best to omit it for now until EnTT introduces some major breaking changes.

[skypjack]

@zaucy can I close this issue?

[zaucy]

thanks for the reminder! with #1147 it can be.

[zaucy]

although the version number is still not automatically updated. Is there a release script I could update?

Typically I would update the version via buildozer like so:

buildozer "set version $VERSION" //MODULE.bazel:%module

I'm willing to put in the work. How do you typically update the version of things like ENTT_VERSION_MINOR? Is it a manual process?

[skypjack]

I usually update version.h, then I read it from cmake.