Add support for spring-io/central-publish-action

* Rework `spring-artifactory-deploy-to-maven-central.yml`
to conditionally call `spring-io/nexus-sync-action` or `spring-io/central-publish-action`
depending on the provided Maven Central secrets
* Remove redundant local `actions\spring-publish-maven-central-portal`
in favor of public `spring-io/central-publish-action`
* Add Central Portal secrets expectations into `spring-artifactory-gradle-release.yml` and `spring-artifactory-maven-release.yml`

Author: artembilan

.github/actions/spring-publish-maven-central-portal/action.yml

@@ -11,10 +11,6 @@ on:
         description: 'The Artifactory Build Number'
         required: true
         type: string
-      releaseVersion:
-        description: 'The release version'
-        required: true
-        type: string
       runner:
         description: 'The runner for job'
         required: false
@@ -28,23 +24,33 @@ on:
         required: false
       OSSRH_STAGING_PROFILE_NAME:
         required: false
-      PORTAL_TOKEN_USERNAME:
+      CENTRAL_TOKEN_USERNAME:
         required: false
-      PORTAL_TOKEN_PASSWORD:
+      CENTRAL_TOKEN_PASSWORD:
         required: false
       JF_ARTIFACTORY_SPRING:
         required: true
 
 env:
   JF_ENV_SPRING: ${{ secrets.JF_ARTIFACTORY_SPRING }}
   OSSRH_S01_TOKEN_USERNAME: ${{ secrets.OSSRH_S01_TOKEN_USERNAME }}
+  CENTRAL_TOKEN_USERNAME: ${{ secrets.CENTRAL_TOKEN_USERNAME }}
   WORKFLOWS_REF: main
 
 jobs:
   deploy-to-maven-central:
     runs-on: ${{ inputs.runner }}
     steps:
 
+      - name: Verify Maven Secrets
+        run: |
+          if [ -z $OSSRH_S01_TOKEN_USERNAME ] || [ -z $CENTRAL_TOKEN_USERNAME ] 
+          then
+            gh run cancel ${{ github.run_id }}
+            echo "::error title=Cannot deploy to Maven Central:: The 'OSSRH_S01_TOKEN_USERNAME' & 'OSSRH_S01_TOKEN_PASSWORD' or 'CENTRAL_TOKEN_USERNAME' & 'CENTRAL_TOKEN_PASSWORD' pair of secrets must be provided"
+            exit 1
+          fi
+
       - uses: actions/checkout@v4
         with:
           repository: spring-io/spring-github-workflows
@@ -60,8 +66,8 @@ jobs:
             --spec utils/release-files-spec.json \
             --spec-vars "buildname=${{ inputs.buildName }};buildnumber=${{ inputs.buildNumber }}"
           
-          jarToCheck=$(find nexus -name "*.jar" -print -quit)
-          jarToCheck=${jarToCheck#nexus}
+          jarToCheck=$(find central_bundle -name "*.jar" -print -quit)
+          jarToCheck=${jarToCheck#central_bundle}
           echo jarToCheck=$jarToCheck >> $GITHUB_OUTPUT
 
       - uses: spring-io/[email protected]
@@ -88,10 +94,9 @@ jobs:
           url: https://repo.maven.apache.org/maven2${{ steps.download-release-files.outputs.jarToCheck }}
 
       - name: Deploy Bundle to Maven Central Portal
-        if: env.PORTAL_TOKEN_USERNAME
-        uses: ./.github/actions/spring-publish-maven-central-portal
+        if: env.CENTRAL_TOKEN_USERNAME
+        uses: spring-io/central-[email protected]
         with:
-          release-version: ${{ inputs.releaseVersion }}
-          token-username: ${{ secrets.PORTAL_TOKEN_USERNAME }}
-          token-password: ${{ secrets.PORTAL_TOKEN_PASSWORD }}
-          deployment-status-interval: '1m'
+          token-name: ${{ secrets.CENTRAL_TOKEN_USERNAME }}
+          token: ${{ secrets.CENTRAL_TOKEN_PASSWORD }}
+          dir: central_bundle

.github/workflows/spring-artifactory-deploy-to-maven-central.yml

@@ -63,6 +63,10 @@ on:
         required: false
       OSSRH_STAGING_PROFILE_NAME:
         required: false
+      CENTRAL_TOKEN_USERNAME:
+        required: false
+      CENTRAL_TOKEN_PASSWORD:
+        required: false
       GPG_PASSPHRASE:
         required: false
       GPG_PRIVATE_KEY:
@@ -136,7 +140,6 @@ jobs:
     with:
       buildName: ${{ needs.staging.outputs.buildName }}
       buildNumber: ${{ needs.staging.outputs.buildNumber }}
-      releaseVersion: ${{ needs.releaseVersion.outputs.releaseVersion }}
       runner: ${{ inputs.runner }}
     secrets: inherit
 

.github/workflows/spring-artifactory-gradle-release.yml

@@ -64,6 +64,10 @@ on:
         required: false
       OSSRH_STAGING_PROFILE_NAME:
         required: false
+      CENTRAL_TOKEN_USERNAME:
+        required: false
+      CENTRAL_TOKEN_PASSWORD:
+        required: false
       GPG_PASSPHRASE:
         required: false
       GPG_PRIVATE_KEY:
@@ -136,7 +140,6 @@ jobs:
     with:
       buildName: ${{ needs.staging.outputs.buildName }}
       buildNumber: ${{ needs.staging.outputs.buildNumber }}
-      releaseVersion: ${{ needs.releaseVersion.outputs.releaseVersion }}
       runner: ${{ inputs.runner }}
     secrets: inherit
 

.github/workflows/spring-artifactory-maven-release.yml

@@ -16,6 +16,8 @@ SPRING_RELEASE_CHAT_WEBHOOK_URL
 OSSRH_S01_TOKEN_USERNAME
 OSSRH_S01_TOKEN_PASSWORD
 OSSRH_STAGING_PROFILE_NAME
+CENTRAL_TOKEN_USERNAME
+CENTRAL_TOKEN_PASSWORD
 GPG_PASSPHRASE
 GPG_PRIVATE_KEY
 ```
@@ -75,7 +77,7 @@ The logic of this release workflow:
 - Call Maven or Gradle (according to the workflow choice for the project in the repository) with the release version extracted from the previous job.
 This job stages released artifacts using JFrog Artifactory plugin into `libs-staging-local` repository on Spring Artifactory and commits `Next development version` to the branch we are releasing against
 - The next job is to [verify staged artifacts](#verify-staged-artifacts)
-- When verification is successful, next job promotes release from staging either to `libs-milestone-local` or `libs-release-local` (by default) (and optional to Maven Central: if `OSSRH_STAGING_PROFILE_NAME` secret is provided) according to the releasing version schema
+- When verification is successful, next job promotes release from staging either to `libs-milestone-local` or `libs-release-local` (by default) (and optional to Maven Central: if `bundleName` input is not provided) according to the releasing version schema
 - Then [spring-finalize-release.yml](.github/workflows/spring-finalize-release.yml) job is executed, which tags release into GitHub, commits next development version, generates release notes using [Spring Changelog Generator](https://github.com/spring-io/github-changelog-generator) excluding repository admins from `Contributors` section.
 The `gh release create` command is performed on a tag for just released version.
 Then spring.io project page is updated for newly released version.