Note that “0.5.0” isn’t technically a valid package version (see <https://docs.racket-lang.org/pkg/Package_Concepts.html#%28tech._version%29|Package Concepts>). raco setup doesn’t complain about this until another package adds a version constraint on your package, unfortunately, so it’s super easy to miss.

(it’s probably also too late to enforce this in raco setup at this point since probably lots of packages (incl. many of my own) are non-compliant)

it doesn’t help that the “version system” the package system uses doesn’t allow communicating incompatible changes without creating new packages