Version changed from snapshot to snapshot without a release version being published #77
Comments
|
To be honest, I don't know why this happened. However, a new release is near. I am still on #42. |
|
@wumpz In theory, you could manually set the version number back to |
|
@cowwoc I know but since I already deployed 4.7-SNAPSHOT versions the next release should be 4.7. |
|
version 4.7 has been released, it could take a while til it is published at maven central |
|
Great! Thank you very much. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the observation
About a month ago, a commit was made that changed the pom version from 4.6-SNAPSHOT to 4.7-SNAPSHOT, but it appears that 4.6 (non-snapshot) was never commited or published to maven central.
To Reproduce
See 89c9f94
Expected behavior
I would like to request that the latest version of master be published to maven central so all of the excellent work you've put into the last 20 commits (and counting) can be utilized.
Thank you!
The text was updated successfully, but these errors were encountered: