`check-version` is slightly different from what I'd expect/want

[rivertam]

With our workflow, we publish beta versions when changes are still in PR but others might want to check it out.

For example, if a package is at 0.24.0, I may make some changes in a PR and publish it as 0.25.0-beta-0. Even before merging it, the main branch will start to fail because, while 0.24.0 is already published, it's not the most "recent" version. This means the workflow step fails.

Is it possible to change it to check if the version is published at all, not just that it's the most recent version?

[mcous]

Duplicate of #35