This is an automated email from the ASF dual-hosted git repository. jdaugherty pushed a commit to branch 7.0.x in repository https://gitbox.apache.org/repos/asf/grails-core.git
commit 5b56997ab352af9747f0496eef7006991adf0b28 Author: James Daugherty <[email protected]> AuthorDate: Wed May 28 20:55:53 2025 -0400 [skip ci] close grails-core staging repo so forge can pull its artifacts --- .github/workflows/release.yml | 20 +++++++++++++++++--- RELEASE.md | 11 ++++++----- 2 files changed, 23 insertions(+), 8 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index c6fe1b4f57..ef76c7b28d 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -81,7 +81,7 @@ jobs: NEXUS_PUBLISH_PASSWORD: ${{ secrets.NEXUS_STAGE_DEPLOYER_PW }} NEXUS_PUBLISH_URL: 'https://repository.apache.org/service/local/' NEXUS_PUBLISH_STAGING_PROFILE_ID: ${{ secrets.STAGING_PROFILE_ID }} - NEXUS_PUBLISH_DESCRIPTION: 'grails-release:${{ steps.release_version.outputs.value }}' + NEXUS_PUBLISH_DESCRIPTION: 'grails-core:${{ steps.release_version.outputs.value }}' SIGNING_KEY: ${{ secrets.GPG_KEY_ID }} working-directory: 'grails-gradle' run: > @@ -93,7 +93,7 @@ jobs: NEXUS_PUBLISH_PASSWORD: ${{ secrets.NEXUS_STAGE_DEPLOYER_PW }} NEXUS_PUBLISH_URL: 'https://repository.apache.org/service/local/' NEXUS_PUBLISH_STAGING_PROFILE_ID: ${{ secrets.STAGING_PROFILE_ID }} - NEXUS_PUBLISH_DESCRIPTION: 'grails-release:${{ steps.release_version.outputs.value }}' + NEXUS_PUBLISH_DESCRIPTION: 'grails-core:${{ steps.release_version.outputs.value }}' SIGNING_KEY: ${{ secrets.GPG_KEY_ID }} working-directory: 'grails-gradle' run: > @@ -110,7 +110,7 @@ jobs: NEXUS_PUBLISH_PASSWORD: ${{ secrets.NEXUS_STAGE_DEPLOYER_PW }} NEXUS_PUBLISH_URL: 'https://repository.apache.org/service/local/' NEXUS_PUBLISH_STAGING_PROFILE_ID: ${{ secrets.STAGING_PROFILE_ID }} - NEXUS_PUBLISH_DESCRIPTION: 'grails-release:${{ steps.release_version.outputs.value }}' + NEXUS_PUBLISH_DESCRIPTION: 'grails-core:${{ steps.release_version.outputs.value }}' SIGNING_KEY: ${{ secrets.GPG_KEY_ID }} run: > ./gradlew @@ -118,6 +118,20 @@ jobs: findSonatypeStagingRepository publishToSonatype aggregateChecksums + - name: "📤 Close Staging Repository" + env: + GRAILS_PUBLISH_RELEASE: 'true' + NEXUS_PUBLISH_USERNAME: ${{ secrets.NEXUS_STAGE_DEPLOYER_USER }} + NEXUS_PUBLISH_PASSWORD: ${{ secrets.NEXUS_STAGE_DEPLOYER_PW }} + NEXUS_PUBLISH_URL: 'https://repository.apache.org/service/local/' + NEXUS_PUBLISH_STAGING_PROFILE_ID: ${{ secrets.STAGING_PROFILE_ID }} + NEXUS_PUBLISH_DESCRIPTION: 'grails-core:${{ steps.release_version.outputs.value }}' + SIGNING_KEY: ${{ secrets.GPG_KEY_ID }} + run: > + ./gradlew + -x initializeSonatypeStagingRepository + findSonatypeStagingRepository + closeSonatypeStagingRepository - name: "🩹Combine checksums" run: | combined_file="build/combined-checksums.txt" diff --git a/RELEASE.md b/RELEASE.md index 00621151b6..187bdee01e 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -35,18 +35,19 @@ During the staging step, we must create a source distribution & stage any binary * This will then scan our commit history and we adjust the release notes per project agreement. * Check "pre-release" * Click "Publish Release" -2. (grails-core) The Github workflow 'release.yml' will kick off, which will run the `publish` job steps. This job will: +2. (grails-core) The Github workflow from `release.yml`, titled `Release - Create grails-core`, will kick off. The `publish` job will: * checkout the project * setup gradle * extract the version # from the tag * run the pre-release workflow (updates gradle.properties to be the version specified by the user) * extract signing secrets from github action variables - * build the project, sign the jar files, and stage them to the necessary location + * build the project, sign the jar files, and stage them to the necessary locations + * add the grails wrapper to the `grails-core` release + * close the staging repository so the `grails-core` artifacts can be accessed 3. Create a matching release in `grails-forge`: * Follow the same steps to create a release in grails-forge. Update any release notes specific to the delegating cli & grails forge. -4. (grails-forge) - * The Github workflow 'release.yml' will kick off, which will run the `publish` job steps. This job will perform the similar steps as above -5. Kick off the `Distribution` workflow in `grails-core`, which will: +4. (grails-forge) The Github workflow `release.yml`, titled `Release - Create grails-forge`, will kick off. This workflow will run a `publish` job that will complete similar steps to the `grails-core` publish job. +5. Kick off the `Release - Grails Distribution` workflow from `distribution.yml` in `grails-core`. This job will: * download the tagged grails source * download the tagged grails-forge source * generate a source distribution meeting the ASF requirements
