Skip to content

Migrate to OSSRH staging api#263

Merged
robinjam merged 2 commits into
mainfrom
jar-migrate-to-ossrh-staging-api
Dec 12, 2025
Merged

Migrate to OSSRH staging api#263
robinjam merged 2 commits into
mainfrom
jar-migrate-to-ossrh-staging-api

Conversation

@robinjam
Copy link
Copy Markdown
Contributor

https://trello.com/c/Fmdfxt2Q/1421-reauthenticate-with-maven-central

Depends on alphagov/notifications-credentials#533

What problem does the pull request solve?

OSSRH is end of life now, all publishes to Maven Central have to go through Central Publisher Portal. This PR updates our Maven config to push via the OSSRH staging API, as that requires minimal changes to our deploy process.

This should allow us to resume pushes to Maven Central.

Checklist

  • I’ve used the pull request template
  • I’ve written unit tests for these changes
  • I’ve updated the documentation in
  • I’ve bumped the version number
    • in src/main/resources/application.properties
    • in pom.xml

ossrh is dead now, ossrh-staging-api is a compatibility API provided by
Maven Central to allow us to continue deploying in the same manner as
before.

The paths to the username/password in notifications-credentials aren't
changing, the new token will just replace the old one.
Fixes a crash when I did a dry run deploy locally
@robinjam robinjam merged commit d73afba into main Dec 12, 2025
1 check passed
@robinjam robinjam deleted the jar-migrate-to-ossrh-staging-api branch December 12, 2025 16:27
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