chore(deps): bump dependencies

[WilliamAGH]

• com.vanniktech.maven.publish: 0.26.0 → 0.35.0
• tools.jackson:jackson-bom: 3.0.0-rc4 → 3.0.3
• org.junit.jupiter:junit-jupiter: 5.11.0 → 6.0.2
• org.junit.platform:junit-platform-launcher: 1.11.0 → 6.0.2

Also migrated to new Central Portal API (SonatypeHost removed in 0.35.0)

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated Gradle Maven publishing plugin to the latest stable version
  • Upgraded Jackson dependency framework to a newer release
  • Updated JUnit testing framework dependencies for improved testing capabilities and stability

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

The pull request updates build.gradle.kts with several dependency and plugin version bumps: Maven publishing plugin from 0.26.0 to 0.35.0, Jackson BOM to 3.0.3, JUnit dependencies to 6.0.2, and revises the Maven publishing configuration API call.

Changes

Cohort / File(s)	Summary
Build Configuration build.gradle.kts	Maven publishing plugin bumped 0.26.0 → 0.35.0; Jackson BOM updated to 3.0.3 from rc4; JUnit Jupiter and platform-launcher upgraded to 6.0.2; Maven publishing config refactored from publishToMavenCentral(SonatypeHost.S01, true) to publishToMavenCentral(automaticRelease = true)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

✨ Build tools climb from old to new,
Versions bump and work runs through,
Jackson stable, JUnit six appears,
Maven publishing perseveres,
Fresh dependencies, our project cheers! 🚀

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the changeset's main purpose: bumping multiple dependencies in the build configuration.
Description check	✅ Passed	The description directly relates to the changeset, listing all four specific dependency updates and explaining the migration to the new Central Portal API.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5d7df8b and 9673e6b.

📒 Files selected for processing (1)

• build.gradle.kts

🔇 Additional comments (4)

build.gradle.kts (4)

72-73: Versions are valid — no issue here.

Both junit-jupiter:6.0.2 and junit-platform-launcher:6.0.2 exist on Maven Central (verified with HTTP 200 responses). JUnit 6 is indeed real, and these artifact versions will resolve successfully during the build. No action needed! 🎉

Likely an incorrect or invalid review comment.

---

17-17: Version 0.35.0 is confirmed—nice upgrade to the Central Portal era! ✨ The changelog confirms SonatypeHost was indeed removed (starting in 0.34.0), and 0.35.0 now enforces Central Portal usage, so the SONATYPE_HOST environment variable or the new mavenCentralPublishing / mavenCentralAutomaticPublishing properties are the way forward. This plugin is battle-tested in the wild and behaves exactly as documented.

---

163-165: API migration to Central Portal is correct — defaults to CENTRAL_PORTAL in v0.35.0.

The shift from publishToMavenCentral(SonatypeHost.S01, true) to publishToMavenCentral(automaticRelease = true) is spot-on! The plugin effectively defaults to CENTRAL_PORTAL as the target, so dropping the explicit host parameter is exactly what the new API expects. Clean and future-proof! 🎉

---

69-71: No action needed — jackson-annotations should stay under com.fasterxml.jackson.

Great news! Jackson 3.x did move most artifacts to the tools.jackson groupId, but jackson-annotations is a deliberate exception. It intentionally remains under com.fasterxml.jackson for compatibility with both Jackson 2.x and 3.x. Your current line 71 using com.fasterxml.jackson.core:jackson-annotations is actually the correct approach! The BOM handles version alignment for all modules, so everything is working as intended here.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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