👷 ci: Use version 5.4.1 in action (#1098)

Author: LogFlames

.github/workflows/Lockfile.yml

@@ -26,7 +26,7 @@ jobs:
             sh.jbang.dev:443
 
       - name: run maven-lockfile
-        uses: chains-project/maven-lockfile@7a3323799269e0f3f1c1921411bb04aadf98eb77 # v5.4.0
+        uses: chains-project/maven-lockfile@352fc01e7c64fdd4766d54931b14f03f958c62da # v5.4.1
         with:
           github-token: ${{ secrets.JRELEASER_GITHUB_TOKEN }}
           include-maven-plugins: true

.github/workflows/LockfilePR.yml

@@ -25,14 +25,14 @@ jobs:
 
       - name: run maven-lockfile
         if: ${{ github.event.pull_request.head.repo.full_name == github.repository }}
-        uses: chains-project/maven-lockfile@7a3323799269e0f3f1c1921411bb04aadf98eb77 # v5.4.0
+        uses: chains-project/maven-lockfile@352fc01e7c64fdd4766d54931b14f03f958c62da # v5.4.1
         with:
           github-token: ${{ secrets.JRELEASER_GITHUB_TOKEN }}
           include-maven-plugins: true
 
       - name: run maven-lockfile (fork/external)
         if: ${{ github.event.pull_request.head.repo.full_name != github.repository }}
-        uses: chains-project/maven-lockfile@7a3323799269e0f3f1c1921411bb04aadf98eb77 # v5.4.0
+        uses: chains-project/maven-lockfile@352fc01e7c64fdd4766d54931b14f03f958c62da # v5.4.1
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
           include-maven-plugins: true

.github/workflows/jreleaser.yml

@@ -64,7 +64,7 @@ jobs:
         if: ${{ github.event.inputs.version == 'major'  || github.event.inputs.version == 'minor' }}
         run: echo "NEXT_VERSION=$(semver next ${{ github.event.inputs.version }} $CURRENT_VERSION)" >> $GITHUB_ENV
       - name: run maven-lockfile (validate lockfile)
-        uses: chains-project/maven-lockfile@6d8b811f6ff24135623a50e511d75dcad2402cf2 # v5.3.6-SNAPSHOT
+        uses: chains-project/maven-lockfile@352fc01e7c64fdd4766d54931b14f03f958c62da # v5.4.1
         with:
             github-token: ${{ secrets.GITHUB_TOKEN }}
             include-maven-plugins: true
@@ -76,7 +76,7 @@ jobs:
       - name: Generate Readme
         run : mvn generate-resources resources:copy-resources
       - name: run maven-lockfile (generate new lockfile for release version)
-        run: mvn io.github.chains-project:maven-lockfile:5.4.0:generate
+        run: mvn io.github.chains-project:maven-lockfile:5.4.1:generate
         shell: bash
       - name: commit changes
         run: |
@@ -125,7 +125,7 @@ jobs:
       - name: Generate Readme
         run : mvn generate-resources resources:copy-resources -q
       - name: run maven-lockfile (generate new lockfile for -SNAPSHOT version)
-        run: mvn io.github.chains-project:maven-lockfile:5.4.0:generate
+        run: mvn io.github.chains-project:maven-lockfile:5.4.1:generate
         shell: bash
 # Commit and push changes
       - name: Commit & Push changes

.github/workflows/regenerate-lockfile.yml

@@ -24,6 +24,6 @@ jobs:
             sh.jbang.dev:443
 
       - name: run maven-lockfile
-        uses: chains-project/maven-lockfile@7a3323799269e0f3f1c1921411bb04aadf98eb77 # v5.4.0
+        uses: chains-project/maven-lockfile@352fc01e7c64fdd4766d54931b14f03f958c62da # v5.4.1
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}

README.md

@@ -169,7 +169,7 @@ jobs:
         runs-on: ubuntu-latest
         steps:
         - name: run maven-lockfile
-          uses: chains-project/maven-lockfile@bdabb56b82feb242cd543af007b333bd8276e44e # v5.3.5
+          uses: chains-project/maven-lockfile@352fc01e7c64fdd4766d54931b14f03f958c62da # v5.4.1
           with:
             github-token: ${{ secrets.JRELEASER_GITHUB_TOKEN }}
             include-maven-plugins: true
@@ -190,7 +190,7 @@ It still works for pull requests from the same repository. Renovate also works w
 Extended github actions example with all available options:
 
 ```yml
-- uses: chains-project/maven-lockfile@bdabb56b82feb242cd543af007b333bd8276e44e # v5.3.5
+- uses: chains-project/maven-lockfile@352fc01e7c64fdd4766d54931b14f03f958c62da # v5.4.1
   with:
     # Required. The GitHub token used to commit the updated lockfile to the repository.
     - github-token: ${{ secrets.JRELEASER_GITHUB_TOKEN }}
@@ -230,11 +230,11 @@ If you are setting the `-SNAPSHOT` version in the release action/script as well
 
 As an example, the steps for the CI in maven-lockfile is:
 * set the version from `X.Y.Z-SNAPSHOT` to `X.Y.Z` in `pom.xml`
-* run maven-lockfile using `mvn io.github.chains-project:maven-lockfile:5.3.5:generate`
+* run maven-lockfile using `mvn io.github.chains-project:maven-lockfile:5.4.1:generate`
 * build and release
 * create `Releasing version X.Y.Z` commit and tag it with `vX.Y.Z`
 * set the version to `X.Y.(Z+1)-SNAPSHOT` in `pom.xml`
-* run maven-lockfile using `mvn io.github.chains-project:maven-lockfile:5.3.5:generate`
+* run maven-lockfile using `mvn io.github.chains-project:maven-lockfile:5.4.1:generate`
 * create `Setting SNAPSHOT version X.Y.(Z+1)-SNAPSHOT` commit
 
 ## Related work