Complete the vanniktech publishing migration - #3
Merged
Merged
Conversation
Finish the in-progress migration to com.vanniktech.maven.publish 0.34.0:
add the mavenPublishing { pom { ... } } block per subproject (values
carried over from the legacy pom.withXml), delete the coexisting legacy
publishing {} / signing {} blocks and the unused ext.isReleaseVersion,
drop the leftover root signing plugin, and add the standard publishing
toggles to gradle.properties.
Per-module POMs (core, cli, mcp) verified semantically identical to the
legacy publication before the legacy blocks were removed.
The snapshot workflow now runs publishToMavenCentral with
ORG_GRADLE_PROJECT_* credentials (org-level secrets already in place).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RaN5r49Rzce1uZRwE9GKqq
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
1 participant
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.
Part of the standardise-build-publishing change (tasks 1.5/3.6) — completes the migration this repo already had in progress.
What
mavenPublishing { pom { … } }block per subproject (core,cli,mcp), carrying over the exact values from the legacypom.withXml.publishing {}/signing {}blocks that coexisted with the vanniktech plugin (they would have produced duplicate publications), the duplicatedext.isReleaseVersion, and the leftover rootsigningplugin.SONATYPE_HOST=CENTRAL_PORTAL/SONATYPE_AUTOMATIC_RELEASE/RELEASE_SIGNING_ENABLEDtogradle.properties.publishToMavenCentralwithORG_GRADLE_PROJECT_*credentials (org-level secrets already provisioned).Verification
./gradlew buildgreen on Gradle 9.2.1 (the repo could not even configure at the pre-WIP HEAD — axion 1.13.6 vs Gradle 9).Merging to develop triggers this repo's first Central Portal snapshot publish.
🤖 Generated with Claude Code
https://claude.ai/code/session_01RaN5r49Rzce1uZRwE9GKqq