bazelbuild/bazel-central-registry#3556 (review):

Given that this is a dependency of pretty much every other module, we should consider releasing a 1.0.0 at some point.

According to the semantic versioning spec:

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backward compatibility, you should probably already be 1.0.0.

Doesn’t this discourage rapid development and fast iteration?

Major version zero is all about rapid development. If you’re changing the API every day you should either still be in version 0.y.z or on a separate development branch working on the next major version.

I agree this repo is ready for 1.0.0 according to those criteria. I suggest:

1. Clarify in the README what API stability means for this repo (for example: adding a constraint is a stable change, removing one not as much)
2. Review open issues and PRs and cautiously consider changes we have high confidence are stable and sustainable.
3. Consider any new suggested changes on this issue
4. Release