From 4e69ef93136c14d461ed7f4a30748d5740900c61 Mon Sep 17 00:00:00 2001 From: Nassim Boutekedjiret Date: Thu, 8 Oct 2026 18:25:38 +0200 Subject: [PATCH 1/2] Update metricshub/workflows to v7 - .github/workflows: maven-build, maven-central-deploy and maven-central-release move from @v4 to @v7. GitHub runners now ship Maven 3.10, and Central snapshot deploys need workflows v7, which declares the central.sonatype.com origin. oss-parent is already 5 and the site already runs on Doxia 2 (maven-site-plugin 4.0.0-M16 with maven-skin-tools 1.8.01, SITE 2.0.0 descriptor), so neither is changed here. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/build.yml | 2 +- .github/workflows/deploy.yml | 2 +- .github/workflows/release.yml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index f90b3a3..e3382b6 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -18,7 +18,7 @@ on: jobs: build: - uses: metricshub/workflows/.github/workflows/maven-build.yml@v4 + uses: metricshub/workflows/.github/workflows/maven-build.yml@v7 with: jdkVersion: "17" debug: ${{ github.event_name == 'workflow_dispatch' && inputs.debug }} diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 1bafd41..3538b03 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -10,7 +10,7 @@ on: jobs: deploy: - uses: metricshub/workflows/.github/workflows/maven-central-deploy.yml@v4 + uses: metricshub/workflows/.github/workflows/maven-central-deploy.yml@v7 with: jdkVersion: "17" secrets: inherit diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 612b361..75ca59c 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -18,7 +18,7 @@ on: jobs: release: - uses: metricshub/workflows/.github/workflows/maven-central-release.yml@v4 + uses: metricshub/workflows/.github/workflows/maven-central-release.yml@v7 with: releaseVersion: ${{ inputs.releaseVersion }} developmentVersion: ${{ inputs.developmentVersion }} From 190f57d0394b4930fdc288719d08d4d64fc122ab Mon Sep 17 00:00:00 2001 From: Bertrand Martin Date: Thu, 8 Oct 2026 18:44:44 +0200 Subject: [PATCH 2/2] Point the release instructions at the Central Portal (#139) The v7 release workflow publishes with central-publishing-maven-plugin (server id `central`); the OSSRH staging console the README referred to is gone. autoRelease stays false, so the pending deployment still has to be published by hand, on the Portal. Co-Authored-By: Claude Fable 5.1 --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 303cbe3..586562d 100644 --- a/README.md +++ b/README.md @@ -50,16 +50,16 @@ git config blame.ignoreRevsFile .git-blame-ignore-revs ## Release instructions -The artifact is deployed to Sonatype's [Maven Central](https://central.sonatype.com/). +The artifact is published to [Maven Central](https://central.sonatype.com/) through the +[Central Portal](https://central.sonatype.com/publishing) with the `central-publishing-maven-plugin` (server Id `central`, +authenticated with a Portal user token). Manual deployments require these credentials in your Maven `settings.xml`. -The actual repository URL is https://s01.oss.sonatype.org/, with server Id `ossrh` and requires credentials to deploy -artifacts manually. +It is strongly recommended to only use [GitHub Actions "Release to Maven Central"](actions/workflows/release.yml) to perform a release: -But it is strongly recommended to only use [GitHub Actions "Release to Maven Central"](actions/workflows/release.yml) to perform a release: - -* Manually trigger the "Release" workflow +* Manually trigger the "Release to Maven Central" workflow * Specify the version being released and the next version number (SNAPSHOT) -* Release the corresponding staging repository on [Sonatype's Nexus server](https://s01.oss.sonatype.org/) +* Publish the pending deployment on the [Central Portal](https://central.sonatype.com/publishing/deployments) + (the workflow uploads and validates it, but does not publish it automatically) * Merge the PR that has been created to prepare the next version ## License