Migrate to central sonatype publishing

[mialeska]

No description provided.

[coderabbitai]

Walkthrough

The Maven build and release configuration was updated to switch from the Nexus staging plugin to the new central publishing plugin. Workflow and POM changes reflect this migration, including updated server identifiers, plugin versions, and removal of explicit repository URLs. No changes were made to the codebase or public API.

Changes

File(s)	Summary
.github/workflows/release-maven-central.yml	Changed distribution from "adopt" to "temurin" in setup-java; updated server-id to "central"; removed -P release from deploy command; added -B --no-transfer-progress.
pom.xml	Removed distributionManagement; replaced Nexus staging plugin (1.7.0) with central publishing plugin (0.8.0); updated plugin configuration keys and flags (serverId→publishingServerId, autoReleaseAfterClose→autoPublish, added waitUntil).

Poem

A hop, a skip, a leap so grand,
From Nexus Staging to Central Land!
No more old URLs to see,
Just plugins new and clean as can be.
The rabbit cheers with every build—
"To Maven Central, dreams fulfilled!" 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 142a828 and 22446ea.

📒 Files selected for processing (1)

• .github/workflows/release-maven-central.yml (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/release-maven-central.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: aquality-automation.aquality-appium-mobile-java (Run tests LOCAL_SERVER)
• GitHub Check: aquality-automation.aquality-appium-mobile-java (Run tests REMOTE_SERVER)
• GitHub Check: aquality-automation.aquality-appium-mobile-java (Analyse code with SonarQube)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.github/workflows/release-maven-central.yml (1)

55-58: Enable non-interactive, faster Maven deploy

Add batch mode flags to cut CI noise and speed up the build.

-  mvn -Dmaven.test.skip=true -Drevision=${{ steps.gitversion.outputs.semVer }} deploy
+  mvn -B --no-transfer-progress -Dmaven.test.skip=true \
+      -Drevision=${{ steps.gitversion.outputs.semVer }} deploy

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between edb8ed2 and 371b892.

📒 Files selected for processing (2)

• .github/workflows/release-maven-central.yml (2 hunks)
• pom.xml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: aquality-automation.aquality-appium-mobile-java (Analyse code with SonarQube)
• GitHub Check: aquality-automation.aquality-appium-mobile-java (Run tests LOCAL_SERVER)
• GitHub Check: aquality-automation.aquality-appium-mobile-java (Run tests REMOTE_SERVER)

🔇 Additional comments (1)

pom.xml (1)

164-172: Plugin version is already up-to-date

0.8.0 (published June 17, 2025) is the latest release of org.sonatype.central:central-publishing-maven-plugin. There is no 1.x series available, so pinning to 0.8.0 is appropriate.

Optional improvement:

• Extract the version into a <central.publishing.version> property for easier future upgrades.

Likely an incorrect or invalid review comment.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud