It is possible to publish a package with empty version to the registry

[kubkon]

I have checked the following:

• I have searched the issues of this repository and believe that this is not a duplicate.
• I have checked that the bug is reproducible with the latest version of Soldeer.

Soldeer Version

soldeer 0.5.2

What Happened?

We use automated pushing of our contracts to the soldeer registry and somehow a bug crept in that erroneously pushed our package with missing version:

I have since repro'ed the issue using a dummy test project and managed to push the project with an empty version:

Expected Behavior

$ forge init
$ soldeer push my-project~ --dry-run
...
error during publishing: package version cannot be empty

(Should return an error that version cannot be empty.)

Reproduction Steps

$ forge init
$ soldeer push my-project~ --dry-run
...
Done!

(Should never succeed.)

Configuration

[mario-eth]

this is interesting, will double check on the backend as well, at least the backend should have caught it. weird. thanks for the fix, will review

[mario-eth]

I'm reopening this so i can keep track to solve on the backend

[kubkon]

@mario-eth would it be possible for you and any other maintainer with access to the backend to yank an invalid published (empty) version? In particular, at vlayer we are currently blocked by this in vlayer package. If you list more versions you will see this bug manifested itself between 0.1.0-nightly-20250127-334f0a0 and 0.1.0-nightly-20250127-5ee6ca8. Any help on this would greatly be appreciated! Thanks!

[mario-eth]

you mean to delete this empty version?

[kubkon]

Yep, exactly right!

[mario-eth]

@mario-eth would it be possible for you and any other maintainer with access to the backend to yank an invalid published (empty) version? In particular, at vlayer we are currently blocked by this in vlayer package. If you list more versions you will see this bug manifested itself between 0.1.0-nightly-20250127-334f0a0 and 0.1.0-nightly-20250127-5ee6ca8. Any help on this would greatly be appreciated! Thanks!

solved, we run the integrity checker.