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

Migrate release to use tokan authn for Maven central #2441

Open
csviri opened this issue Jun 17, 2024 · 1 comment
Open

Migrate release to use tokan authn for Maven central #2441

csviri opened this issue Jun 17, 2024 · 1 comment
Assignees

Comments

@csviri
Copy link
Collaborator

csviri commented Jun 17, 2024

The release is now failing because of this.

Related email:

Dear Maven Central publisher,

We are making changes to the OSSRH authentication backend. For most users this should be a transparent process, and you should be able to continue to use your existing username and password to connect the Nexus UI. In case you need to update your password, please follow our documentation.

To configure a publisher’s plugin authentication you would need to update your plugin settings to use a user token instead of the Nexus UI username and password login.

For more information about publishing to legacy OSSRH please consult our documentation at https://central.sonatype.org/register/legacy/

Thank you,
The Central Team

@csviri csviri self-assigned this Jun 17, 2024
@csviri
Copy link
Collaborator Author

csviri commented Jun 17, 2024

Fixed it to migrating credentials to toke, but the release plugin is also archived github action, that should be fixed too.

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

No branches or pull requests

1 participant