Skip to content
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

Switch publishing to s01.oss.sonatype.org #135

Merged
merged 1 commit into from
Feb 8, 2022
Merged

Switch publishing to s01.oss.sonatype.org #135

merged 1 commit into from
Feb 8, 2022

Conversation

armanbilge
Copy link
Member

No description provided.

ThisBuild / tlBaseVersion := "0.11"
ThisBuild / tlBaseVersion := "0.12"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a breaking change.

@rossabaker rossabaker merged commit fccb2c9 into main Feb 8, 2022
@rossabaker
Copy link
Member

Okay, I'm going to publish from organization secrets. 🤞

@armanbilge armanbilge deleted the topic/s01 branch February 8, 2022 03:27
@armanbilge
Copy link
Member Author

The snapshot publish just failed. Did you delete the secrets from this repository?

@armanbilge
Copy link
Member Author

Oh, but the tag seems to have worked! 😁

@rossabaker
Copy link
Member

rossabaker commented Feb 8, 2022

I think I merged, then cleared out the old secrets, then tagged... though the old secrets should have had rights on the new host too.

@armanbilge
Copy link
Member Author

They wouldn't have I think. oss.sonatype.org and s01.oss.sonatype.org have independent credential systems.

@rossabaker
Copy link
Member

From the Sonatype ticket:

NOTE: all users who previously had access to this groupId should now be able to access it on the new host AND I've granted http4s-bot permissions as well, but ONLY on the new host.

🤷 It doesn't really matter, because the one we want to use works on the host we want to use it on.

@armanbilge
Copy link
Member Author

It's confusing. The users have permissions, but the credentials do not. I ran into this when you got me publishing rights for Typelevel and my s01 credentials didn't work. I had to log-in to the old system and generate a separate pair of credentials.

@armanbilge
Copy link
Member Author

Oh, apologies, I'm confusing user credentials vs user tokens. I exclusively use the latter. Also from the ticket:

Also, keep in mind that if you are using Tokens instead of username/credentials to publish you will need to generate new tokens and replace those in your current setup from here

@rossabaker
Copy link
Member

Oh, I usually set up tokens. It was almost certainly that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants