Please Release New Versions When Making Breaking Changes

[hoffm386]

Hello, I am working on troubleshooting an issue that occurred due to e2bd391.

I built a Docker image that used aequitas==1.0.0 and numpy==1.23.5 earlier this year.

Then this week, I attempted to build a new image from this same specification. The build failed, because when that commit was made, the Aequitas NumPy dependency changed from numpy==1.23.5 to numpy>=1.24.4. Thus, the exact version of NumPy that was required by this package previously, 1.23.5, was no longer permitted as the NumPy version after this change.

This level of change in dependencies should trigger a new release of Aequitas. End users should reasonably expect that aequitas==1.0.0 is going to have the same dependencies in December that it had in August.

If you had bumped the version, even just to 1.0.1, I would not be having this issue. However a more appropriate version might be 1.1.0, because patch updates should only be used for bug fixes, whereas minor updates add functionality. See Semantic Versioning documentation.

Please follow best practices for releases going forward!