Cut over to the Code Genome Project for publishing and org.openrewrite resolution - #467
Merged
Conversation
Registers CGP's S3 bucket as a Maven publishing repository, mirroring org.openrewrite.build.publish-cgp, and points the CI publish-snapshots step at it with the CGP AWS credentials.
…Central Drops the gradle-nexus publish plugin and its nexusPublishing block, which were vestigial: org.openrewrite:plugin was never on Maven Central, as releases go to the Gradle Plugin Portal via publishPlugins. Removes the Sonatype snapshots repository and excludes org.openrewrite and io.moderne from Maven Central and the plugin portal (which proxies Central) whenever CGP credentials are configured, so those groups resolve from CGP alone.
timtebeek
marked this pull request as ready for review
August 25, 2026 21:28
MBoegers
approved these changes
Aug 26, 2026
timtebeek
added a commit
that referenced
this pull request
Aug 26, 2026
…tal (#474) * Publish releases to the Code Genome Project as well as the plugin portal The CGP cutover in #467 pointed the ci.yml snapshot step at publishPluginMavenPublicationToCgpRepository but left publish.yml alone, so tagged releases only ran publishPlugins. v7.40.0 landed on the Gradle Plugin Portal and never reached artifacts.codegenomeproject.org. Adds the CGP publish task and its AWS credentials to both the candidate and release steps, mirroring ci.yml. * Drop the publish-candidate step from the publish workflow
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.
Completes the cutover to the Code Genome Project: snapshots publish there instead of Sonatype, nothing publishes to Sonatype or Maven Central at all, and
org.openrewrite/io.moderneartifacts are no longer consumed from Maven Central.Publishing
plugin/build.gradle.ktsregisters CGP's S3 bucket as a Maven publishing repository, mirroringorg.openrewrite.build.publish-cgp— this repo can't apply that plugin, since it wires nebula andgradle-nexus.publish-plugindirectly. The host is region-qualified because Gradle's S3 transport otherwise defaults tous-east-1..github/workflows/ci.ymlpublishes:plugin:publishPluginMavenPublicationToCgpRepositorywith theCGP_AWS_*org secrets, replacing the Sonatype and OSSRH signing credentials. The signing properties were dead already — nosigningplugin is applied anywhere in this build.build.gradle.ktsdropsio.github.gradle-nexus.publish-pluginand itsnexusPublishingblock. These were vestigial:org.openrewrite:pluginwas never on Maven Central (repo1.maven.org404s for it), because releases go to the Gradle Plugin Portal viapublishPluginsand nothing ever invokedpublishToSonatype.cgpis now the only Maven publishing repository.Resolution
central.sonatype.com/repository/maven-snapshotsrepository.org.openrewriteandio.modernefrom bothmavenCentralandgradlePluginPortal(which proxies Central) whenever CGP credentials are configured, so those groups resolve from CGP alone. This follows thecodegenomeConfiguredpattern fromrewrite-build-gradle-plugin— gating on credentials keeps fork PRs, which receive no secrets, building against Central.mavenCentralstays for third-party dependencies.Verification
Run locally with real CGP credentials, so the credentialed path was genuinely exercised rather than falling back to Central:
org.openrewritedependency resolves from CGP at8.91.0-SNAPSHOTwith Central excluded, including theorg.openrewrite.gradle.toolingsubgroup.-Preleasing):latest.releaseresolves to8.90.4from CGP.final publishPlugins --dry-runagainst a throwaway local tag) is unchanged and contains no Sonatype step.*Sonatype*tasks are gone;publishPluginMavenPublicationToCgpRepositoryresolves through jar → javadocJar → sourcesJar → POM → publish. The build still configures cleanly with no AWS credentials present.Worth flagging
artifacts.codegenomeproject.orgreturns 401 anonymously where the Sonatype snapshot repo did not, so anyone consumingorg.openrewrite:plugin:*-SNAPSHOTwithout credentials needs a CGP download token. README updated accordingly.github.event_name != 'pull_request', so the first real upload happens on merge to main.cgpis the only publishing repository,:plugin:publishwould also push the plugin marker (publishRewritePluginMarkerMavenPublicationToCgpRepository), which would make snapshots consumable viaplugins { id("org.openrewrite.rewrite") version "…-SNAPSHOT" }and retire theuseModuleworkaround in the README. Left out as out of scope; happy to add.