Merge pull request #471 from siom79/branch-0.25.0

siom79 · web-flow · commit aac58ccfad79 · 2025-11-23T14:07:13.000+01:00
Branch 0.25.0
diff --git a/.github/workflows/gh-release.yml b/.github/workflows/gh-release.yml
@@ -22,11 +22,11 @@ jobs:
               run: mvn -B package
 
             - name: Artefakte sammeln
-              run: mkdir build && cp target/*.jar build/
+              run: mkdir japicmp/build && cp japicmp/target/japicmp*.jar japicmp/build/
 
             - name: Release erstellen
               uses: softprops/action-gh-release@v2
               with:
-                  files: build/*.jar
+                  files: japicmp/build/*.jar
               env:
                   GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/README.md b/README.md
@@ -144,6 +144,7 @@ Use the maven site plugin (`mvn site`) to generate the following reports:
 ## Release
 
 This is the release procedure:
+* Create a branch named release-v0.XX.X
 * Update ReleaseNotes.md.
 * If necessary: Set the release version in maven:
 ```bash
@@ -160,6 +161,7 @@ python3 release.py --release-version <release-version> --old-version <old-versio
 	* Download released artifact from staging repository.
 	* Close and release staging repository if sanity checks are successful.
 * Update maven site report with [Action](https://github.com/siom79/japicmp/actions/workflows/mvn-site.yml)
+* Run Github Release [Action](https://github.com/siom79/japicmp/actions/workflows/gh-release.yml)
 
 If the release fails, the version must be reverted and the tag created during the release has to be deleted:
 ```bash
