Bug: Current version on MODULE.bazel cannot be used as a dep

[eclipse-impl]

Describe the bug:

MODULE.bazel states that the component is on version 0.0.3. When one adds a dep to it on another component:

bazel_dep(name = "score_logging", version = "0.0.3")

One will get the following build error:

ERROR: Error computing the main repository mapping: module libatomic@1.0 not found in registries:
* https://raw.githubusercontent.com/eclipse-score/bazel_registry/main/modules/libatomic/1.0/MODULE.bazel: not found
* https://bcr.bazel.build/modules/libatomic/1.0/MODULE.bazel: not found

It's not easy to spot where the problem is, until one finds the module's declaration on Bazel Registry. There the dependency exists (contrary to what is observed on main branch) and has local_path_override, which would never work.

There's also no clear definition on how to solve the problem, until one notices that there's another release, numbered 0.0.4, that has this dependency commented out.

Then it gets clear that there was a release problem, and a new version has been issued to fix it. However, this new version should be reflected on the main branch, otherwise many more people will stumble upon the problem and waste time.

Fix: Update the MODULE.bazel file on main branch to version 0.0.4, to make version 0.0.3 officially deprecated.

Steps to reproduce the behavior:

1. Include this module as a dependency to another one, stating the current version mentioned on branch main.
2. Build any target.

Observed behavior:

Dependency is not found:

ERROR: Error computing the main repository mapping: module libatomic@1.0 not found in registries:
* https://raw.githubusercontent.com/eclipse-score/bazel_registry/main/modules/libatomic/1.0/MODULE.bazel: not found
* https://bcr.bazel.build/modules/libatomic/1.0/MODULE.bazel: not found

Expected behavior

Module won't present dangling dependencies.

Occurrence:

Always

Attachments / Logs: