Use GitHub releases to create a release. (#1531)

Author: bodiam

.github/workflows/release-from-tag.yml

@@ -0,0 +1,70 @@
+name: Release from GitHub Release
+on:
+  release:
+    types: [created]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      packages: write
+    steps:
+      - name: Get release version from tag
+        id: get_version
+        run: |
+          RELEASE_VERSION=${GITHUB_REF#refs/tags/}
+          echo "Extracted version: $RELEASE_VERSION"
+          # Validate semver format (MAJOR.MINOR.PATCH)
+          echo "$RELEASE_VERSION" | grep -P '^2\.[0-9]+\.[0-9]+$'
+          echo "release_version=$RELEASE_VERSION" >> $GITHUB_OUTPUT
+
+      - uses: actions/checkout@v4
+      - name: Set up JDK 17
+        uses: actions/setup-java@v4
+        with:
+          java-version: '17'
+          distribution: 'temurin'
+          cache: maven
+      
+      - name: Set projects Maven version to GitHub Release version
+        run: mvn versions:set "-DnewVersion=${{ steps.get_version.outputs.release_version }}"
+      
+      - name: Deploy to Maven Central Repository
+        uses: actions/setup-java@v4
+        with:
+          java-version: '17'
+          distribution: 'temurin'
+          cache: maven
+          server-id: ossrh
+          server-username: MAVEN_USERNAME
+          server-password: MAVEN_PASSWORD
+          gpg-private-key: ${{ secrets.GPG_SIGNING_KEY }}
+      
+      - name: Publish to the Maven Central Repository
+        run: mvn --batch-mode clean deploy -Possrh
+        env:
+          MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
+          MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
+      
+      - name: Update Release Notes
+        id: changelog
+        uses: metcalfc/changelog-generator@v4.6.2
+        with:
+          mytoken: "${{ secrets.GITHUB_TOKEN }}"
+      
+      - name: Update GitHub Release with Changelog
+        uses: octokit/request-action@v2.x
+        with:
+          route: PATCH /repos/{repo}/releases/{release_id}
+          repo: ${{ github.repository }}
+          release_id: ${{ github.event.release.id }}
+          body: |
+            ### Things that changed in this release
+            ${{ steps.changelog.outputs.changelog }}
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+  
+  call_pom_update:
+    needs: publish
+    uses: ./.github/workflows/pom_update.yml

RELEASE_PROCESS.md

@@ -0,0 +1,32 @@
+# Release Process
+
+## Creating a New Release
+
+The release process is now driven by GitHub Releases:
+
+1. Go to the [Releases page](https://github.com/datafaker-net/datafaker/releases) of the repository
+2. Click on "Draft a new release"
+3. Create a new tag in the format `2.x.y` (where x and y are the minor and patch version numbers)
+4. Set the release title (can be the same as the tag)
+5. Add a description of the changes (optional - will be enhanced by automated changelog)
+6. Click "Publish release"
+
+The automated workflow will:
+1. Extract the version from the tag
+2. Update the Maven project version
+3. Build and deploy to Maven Central
+4. Generate a changelog and add it to the release notes
+5. Create a PR to update the pom.xml to the next SNAPSHOT version
+
+## Requirements
+
+- The tag must follow semver format: `2.x.y` (where x and y are numeric)
+- GitHub Release creation permissions are required to trigger the workflow
+- All required secrets must be configured in the repository settings
+
+## Verification
+
+After publishing a release:
+1. Check the workflow run in the Actions tab
+2. Verify the artifact is published to Maven Central
+3. Review the PR created to update the SNAPSHOT version