circe/circe-yaml

v1.15.0 is on Maven Central

armanbilge opened this issue · 7 comments

armanbilge commented

https://repo1.maven.org/maven2/io/circe/circe-yaml_3/1.15.0/

Unfortunately it is too late to pretend this "didn't happen". Not sure what the best path forward is 😕

satorg commented

@armanbilge could you provide a clue why v1.15.0 is so concerning please? Perhaps I missed something – have no idea now.

armanbilge commented

It looks like the tag was deleted in what I'm guessing was an attempt to "retract" the release, in favor of the intended 0.15.0.

https://github.com/circe/circe-yaml/tags

But since v1.15.0 is on Maven Central, all the tooling sees it, so it's too late to ignore it. Either this needs to become the new blessed release, or we need to advance to a version number greater than that.

Edit: FTR, this is the job that released v1.15.0. At that time, the tag existed.

https://github.com/circe/circe-yaml/actions/runs/6722392484/job/18270374329

  • 👍2
satorg commented

yeah, I see now. Thanks for the clarification.
Perhaps (imo), since it is on Maven Central anyway it would probably better to restore the deleted tag back.

  • 👍1
j-mie6 commented

congrats on the 15th stable release! Always nice to get out of 0.x 🎉

  • 🎉4
mcanlas commented

I was going to say why not delete it and then Googled as such, so this came up...

https://stackoverflow.com/questions/9789611/removing-an-artifact-from-maven-central

I guess if we're committing to it, it makes this a non-issue and we can close?

armanbilge commented

I guess if we're committing to it, it makes this a non-issue and we can close?

That's precisely my point: we can't close because currently the repository is pretending like it's not committed to that release. i.e. the v1.15.0 tag was deleted as if it never happened. We can close this issue after we actually acknowledge that release, one way or another.