-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Releases are failing #986
Comments
@matejcerny can you please have a look too ? |
Sadly we will need a help from @gvolpe as I don't have access to sonatype. |
All releases are stuck until we fix this, since it's the second time I'd say that at least you @matejcerny should have sonatype access. |
I have contacted Gabriel via email. In the meantime, I made you an admin @geirolz as you are the most active anyway. |
Fixed: https://github.com/profunktor/fs2-rabbit/actions/runs/11385486599/job/31822567302 re: access to sonatype: this is my private account, not something I can share. Also, the UI/UX is quite bad on sonatype, not sure if they would allow share publishing access to the same target |
I noticed the latest release failed so I went into Sonatype, deleted all the snapshot repositories and retried, but it's still failing: https://github.com/profunktor/fs2-rabbit/actions/runs/11532300798/job/32143367201 This process is so brittle. It needs to be fixed either in Sonatype or if possible in I deleted the snapshot repository once again, feel free to retry later on or cut a new minor release. If it doesn't work, I would suggest start publishing new releases under a new namespace so you can have admin access to Sonatype. |
We have already dealt with this error. Last time, there were some "dirty" files in Git that were generated by a plugin. This time it's because of a scalafmt. |
I have fixed and re-released it: https://oss.sonatype.org/service/local/repositories/releases/content/dev/profunktor/fs2-rabbit_3/5.3.0/fs2-rabbit_3-5.3.0.jar |
All releases since a while are failing with this message:
Any idea ?
Did we update the auth method to Sonatype from username-password to user token ?
https://central.sonatype.org/publish/generate-token/
The text was updated successfully, but these errors were encountered: