Bump v0.7.1 to v0.7.2 for release

Signed-off-by: Marco Franssen <marco.franssen@philips.com>

.github/workflows/ci.yaml

@@ -199,7 +199,7 @@ jobs:
 
     steps:
       - name: Generate provenance for Release
-        uses: philips-labs/slsa-provenance-action@v0.7.1
+        uses: philips-labs/slsa-provenance-action@v0.7.2
         with:
           command: generate
           subcommand: github-release
@@ -249,7 +249,7 @@ jobs:
           cosign-release: 'v1.5.1'
 
       - name: Generate provenance for ${{ matrix.repo }}
-        uses: philips-labs/slsa-provenance-action@v0.7.1
+        uses: philips-labs/slsa-provenance-action@v0.7.2
         with:
           command: generate
           subcommand: container

.github/workflows/example-publish.yaml

@@ -26,7 +26,7 @@ jobs:
         uses: actions/download-artifact@v2
 
       - name: Generate provenance
-        uses: philips-labs/slsa-provenance-action@v0.7.1
+        uses: philips-labs/slsa-provenance-action@v0.7.2
         with:
           command: generate
           subcommand: files

README.md

@@ -109,15 +109,15 @@ See all available images [here.](https://hub.docker.com/r/philipssoftware/slsa-p
 Run the Docker image by doing:
 
 ```sh
-docker run philipssoftware/slsa-provenance:v0.7.1
+docker run philipssoftware/slsa-provenance:v0.7.2
 ```
 
 **GitHub Container Registry**
 See all available images [here.](https://github.com/philips-labs/slsa-provenance-action/pkgs/container/slsa-provenance)
 Run the Docker image by doing:
 
 ```sh
-docker run ghcr.io/philips-labs/slsa-provenance:v0.7.1
+docker run ghcr.io/philips-labs/slsa-provenance:v0.7.2
 ```
 
 The Docker image includes the working binary that can be executed by using the ``slsa-provenance`` command.
@@ -145,7 +145,7 @@ The easiest way to use this action is to add the following into your workflow fi
 
     steps:
       - name: Generate provenance for Release
-        uses: philips-labs/slsa-provenance-action@v0.7.1
+        uses: philips-labs/slsa-provenance-action@v0.7.2
         with:
           command: generate
           subcommand: files
@@ -180,7 +180,7 @@ The easiest way to use this action is to add the following into your workflow fi
           path: extra-materials/
 
       - name: Generate provenance
-        uses: philips-labs/slsa-provenance-action@v0.7.1
+        uses: philips-labs/slsa-provenance-action@v0.7.2
         with:
           command: generate
           subcommand: files

RELEASE.md

@@ -5,7 +5,7 @@
 To make a new release you can make use of the following `make` task.
 
 ```bash
-make gh-release NEW_VERSION=v0.7.1 OLD_VERSION=v0.5.0 DESCRIPTION="A test release to see how it works"
+make gh-release NEW_VERSION=v0.7.2 OLD_VERSION=v0.5.0 DESCRIPTION="A test release to see how it works"
 ```
 
 `NEW_VERSION` the version that you want to release.
@@ -15,7 +15,7 @@ make gh-release NEW_VERSION=v0.7.1 OLD_VERSION=v0.5.0 DESCRIPTION="A test releas
 Visit <https://github.com/philips-labs/slsa-provenance-action/releases>.
 Edit the release and save it to publish to GitHub Marketplace.
 
-> :warning: **NOTE:** when you need to test some changes in `.goreleaser.yml`, also apply the changes to `.goreleaser.draft.yml`. Then make sure your new `tag` ends with `-draft` (e.g.: `v0.7.1-draft`) to make a draft release to not notify our consumers when testing updates to the release process.
+> :warning: **NOTE:** when you need to test some changes in `.goreleaser.yml`, also apply the changes to `.goreleaser.draft.yml`. Then make sure your new `tag` ends with `-draft` (e.g.: `v0.7.2-draft`) to make a draft release to not notify our consumers when testing updates to the release process.
 
 ### ⚠ Important alert for MacOS users ⚠
 

install-slsa-provenance.sh

@@ -21,7 +21,7 @@ INSTALL_PATH=${INSTALL_PATH:-$(realpath ./.slsa-provenance)}
 
 mkdir -p "${INSTALL_PATH}"
 
-VERSION=v0.7.1
+VERSION=v0.7.2
 RELEASE="https://github.com/philips-labs/slsa-provenance-action/releases/download/${VERSION}"
 
 if [[ "$VERSION" == *-draft ]] ; then