Repository navigation
Fix 4.x release: Migrate to Maven Central Publishing API - #1704
Closed
ricardozanini wants to merge 2 commits into
Closed
ricardozanini wants to merge 2 commits into
ricardozanini wants to merge 2 commits into
Conversation
Migrates from legacy Sonatype OSSRH to new Maven Central Publishing API. This resolves the 402 Payment Required error by using the new publishing system that respects the approved exemption limits (10 releases, 100 MB, 8160 files monthly for io.serverlessworkflow). Changes: - Replace nexus-staging-maven-plugin with central-publishing-maven-plugin - Update workflow server-id from 'ossrh' to 'central' - Remove distributionManagement section (handled by new plugin) - Simplify release:perform invocation Signed-off-by: GitHub Action <action@github.com>
The plugin was only in pluginManagement, not in the active build/plugins section, causing maven-deploy-plugin to run instead. This resulted in: "repository element was not specified in the POM inside distributionManagement" Moving the plugin configuration to build/plugins ensures it's active during the release process. Signed-off-by: GitHub Action <action@github.com>
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Central publication must wait for final publication status to avoid falsely successful releases.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (1)
What changed in this PR
Migrates 4.x releases from OSSRH to the Maven Central Publishing API to resolve release failures.
Changes:
- Adds and configures
central-publishing-maven-plugin0.11.0. - Removes legacy Nexus distribution management.
- Updates release credentials and simplifies publishing.
| File | Summary |
|---|---|
pom.xml |
Configures Central publishing; unresolved critical and moderate findings require waiting for published rather than uploaded (1 vote each). |
.github/workflows/release.yml |
Uses the central server configuration and simplified release command. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| <configuration> | ||
| <publishingServerId>central</publishingServerId> | ||
| <autoPublish>true</autoPublish> | ||
| <waitUntil>uploaded</waitUntil> |
Collaborator
Author
|
Closing - PR #1700 was already merged, so 4.x already has these changes |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves the 402 Payment Required error when releasing from the 4.x branch.
Problem
The 4.x branch was still using the legacy Sonatype OSSRH publishing endpoint, which now enforces publishing limits with a 402 error. The approved exemption (10 releases, 100 MB, 8160 files monthly for io.serverlessworkflow) only applies to the new Maven Central Publishing API.
Solution
Backported the Maven Central migration from main (originally done in f20021f) to the 4.x branch:
nexus-staging-maven-pluginwithcentral-publishing-maven-pluginv0.11.0server-idfromossrhtocentraldistributionManagementsection (handled by new plugin)release:performinvocationTesting
After merge, retry the 4.3.0.Final release - it should now publish successfully through the new API that respects the exemption limits.