Today I released v7.2.3, which eagerly removes compatibility_level via #1815, since compatibility_level is a no-op in Bazel 8.6.0 and will be in 9.1.0:

• https://github.com/bazel-contrib/rules_scala/releases/tag/v7.2.3
• https://registry.bazel.build/modules/rules_scala/7.2.3

I had to override the compatibility_level check in bazelbuild/bazel-central-registry#7729 to unblock the release flow. Only after that did I ask myself, "Will this break any of our users?"

Pinging @meteorcloudy and @Wyverald for their opinions. I could yank 7.2.3 and restore compatibility_level = "7" if this might become a problem.