New release candidate: fix publishing to sonatype

[Pfeil]

The previous candidate was not published due to changes in the sonartype repository. This RC aims to fix this.

Summary by CodeRabbit

• Chores
  • Updated build tooling dependencies to the latest compatible versions to ensure smoother builds and dependency integrity.
  • Adjusted publishing configuration to use a customized staging/central repository for artifact distribution and improved release routing.

[coderabbitai]

Walkthrough

Updated Gradle plugin and dependency versions, and replaced the default Sonatype sonatype() publishing configuration with explicit Nexus staging and snapshot repository URLs for release publishing.

Changes

Cohort / File(s)	Summary
Buildfile version bumps build.gradle	Bumped plugin io.freefair.maven-publish-java from 9.0.0 to 9.1.0; updated dependency com.github.fslev:json-compare from 7.1 to 7.2.
Nexus publishing configuration gradle/profile-release.gradle	Replaced sonatype() default with explicit sonatype { nexusUrl = https://ossrh-staging-api.central.sonatype.com/service/local/; snapshotRepositoryUrl = https://central.sonatype.com/repository/maven-snapshots/ }.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer/CI
    participant Gradle as Gradle Build
    participant Plugin as maven-publish / freefair plugin
    rect rgb(235,245,255)
    note right of Plugin: Before
    Dev->>Gradle: run publish
    Gradle->>Plugin: use sonatype() default
    Plugin->>Sonatype: publish to default Sonatype endpoints
    end
    rect rgb(245,255,235)
    note right of Plugin: After (changed)
    Dev->>Gradle: run publish
    Gradle->>Plugin: use explicit nexusUrl & snapshotRepositoryUrl
    Plugin->>Nexus: publish to configured staging & snapshot URLs
    end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify plugin 9.1.0 compatibility and changelog for breaking changes.
• Confirm json-compare:7.2 behavior matches expectations.
• Validate the Nexus URLs and credentials in CI/release pipeline (gradle/profile-release.gradle).

Poem

🐰 In the meadow of builds I hop and play,
A plugin nudged up by a bright new day,
Repos rerouted to staging's light,
Snapshots sheltered safe at night,
I nibble changes — release takes flight! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main objective of the PR: fixing Sonatype publishing configuration issues for a release candidate.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch development

---

📜 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 3754b1e and dae2871.

📒 Files selected for processing (1)

• build.gradle (2 hunks)

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

• build.gradle

⏰ 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). (7)

• GitHub Check: build (windows-latest, 21)
• GitHub Check: Analyze (java)
• GitHub Check: build (ubuntu-latest, 21)
• GitHub Check: build (windows-latest, 17)
• GitHub Check: build (windows-latest, 21)
• GitHub Check: build (windows-latest, 17)
• GitHub Check: build (macos-latest, 17)

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coveralls]

Pull Request Test Coverage Report for Build #588

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 91.327%

---

Totals
Change from base Build #577:	0.0%
Covered Lines:	2243
Relevant Lines:	2456

---

💛 - Coveralls