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

CIWE: FIX: Sonatype now requires token instead of userid and password #906

Open
Tracked by #131
jeromy-cannon opened this issue Jul 1, 2024 · 0 comments
Open
Tracked by #131
Assignees
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs P1 High priority issue. Required to be completed in the assigned milestone.

Comments

@jeromy-cannon
Copy link
Contributor

jeromy-cannon commented Jul 1, 2024

Deploy release for 0.28.3 fails -> workflow run

Execution failed for task ':fullstack-base-api:publishMavenPublicationToSonatypeRepository'.
> Failed to publish publication 'maven' to repository 'sonatype'
   > Could not PUT 'https://oss.sonatype.org/service/local/staging/deploy/maven2/com/hedera/fullstack/fullstack-base-api/0.28.3/fullstack-base-api-0.28.3.jar'. Received status code 401 from server: Content access is protected by token

workflow and gradle build needs to be updated and new secret added, old secrets removed.

@github-project-automation github-project-automation bot moved this to 🆕 New in FST Suite Jul 1, 2024
@jeromy-cannon jeromy-cannon changed the title CIWE: BUG: Sonatype now requires token instead of userid and password CIWE: FIX: Sonatype now requires token instead of userid and password Jul 1, 2024
@jeromy-cannon jeromy-cannon added Bug A error that causes the feature to behave differently than what was expected based on design docs P1 High priority issue. Required to be completed in the assigned milestone. labels Jul 1, 2024
@jeromy-cannon jeromy-cannon moved this from 🆕 New to 🔖 Ready in FST Suite Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs P1 High priority issue. Required to be completed in the assigned milestone.
Projects
Status: 🔖 Ready
Development

No branches or pull requests

2 participants