Skip to content

Commit 3645ec0

Browse files
committed
Bump v0.7.0 to v0.7.1 for release
Signed-off-by: Marco Franssen <marco.franssen@philips.com>
1 parent 26286f0 commit 3645ec0

File tree

4 files changed

+8
-8
lines changed

4 files changed

+8
-8
lines changed

.github/workflows/example-publish.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ jobs:
2626
uses: actions/download-artifact@v2
2727

2828
- name: Generate provenance
29-
uses: philips-labs/slsa-provenance-action@v0.7.0
29+
uses: philips-labs/slsa-provenance-action@v0.7.1
3030
with:
3131
command: generate
3232
subcommand: files

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -109,15 +109,15 @@ See all available images [here.](https://hub.docker.com/r/philipssoftware/slsa-p
109109
Run the Docker image by doing:
110110

111111
```sh
112-
docker run philipssoftware/slsa-provenance:v0.7.0
112+
docker run philipssoftware/slsa-provenance:v0.7.1
113113
```
114114

115115
**GitHub Container Registry**
116116
See all available images [here.](https://github.com/philips-labs/slsa-provenance-action/pkgs/container/slsa-provenance)
117117
Run the Docker image by doing:
118118

119119
```sh
120-
docker run ghcr.io/philips-labs/slsa-provenance:v0.7.0
120+
docker run ghcr.io/philips-labs/slsa-provenance:v0.7.1
121121
```
122122

123123
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
145145

146146
steps:
147147
- name: Generate provenance for Release
148-
uses: philips-labs/slsa-provenance-action@v0.7.0
148+
uses: philips-labs/slsa-provenance-action@v0.7.1
149149
with:
150150
command: generate
151151
subcommand: files
@@ -180,7 +180,7 @@ The easiest way to use this action is to add the following into your workflow fi
180180
path: extra-materials/
181181

182182
- name: Generate provenance
183-
uses: philips-labs/slsa-provenance-action@v0.7.0
183+
uses: philips-labs/slsa-provenance-action@v0.7.1
184184
with:
185185
command: generate
186186
subcommand: files

RELEASE.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
To make a new release you can make use of the following `make` task.
66

77
```bash
8-
make gh-release NEW_VERSION=v0.7.0 OLD_VERSION=v0.5.0 DESCRIPTION="A test release to see how it works"
8+
make gh-release NEW_VERSION=v0.7.1 OLD_VERSION=v0.5.0 DESCRIPTION="A test release to see how it works"
99
```
1010

1111
`NEW_VERSION` the version that you want to release.
@@ -15,7 +15,7 @@ make gh-release NEW_VERSION=v0.7.0 OLD_VERSION=v0.5.0 DESCRIPTION="A test releas
1515
Visit <https://github.com/philips-labs/slsa-provenance-action/releases>.
1616
Edit the release and save it to publish to GitHub Marketplace.
1717

18-
> :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.0-draft`) to make a draft release to not notify our consumers when testing updates to the release process.
18+
> :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.
1919
2020
### ⚠ Important alert for MacOS users ⚠
2121

install-slsa-provenance.sh

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ INSTALL_PATH=${INSTALL_PATH:-$(realpath ./.slsa-provenance)}
2121

2222
mkdir -p "${INSTALL_PATH}"
2323

24-
VERSION=v0.7.0
24+
VERSION=v0.7.1
2525
RELEASE="https://github.com/philips-labs/slsa-provenance-action/releases/download/${VERSION}"
2626

2727
if [[ "$VERSION" == *-draft ]] ; then

0 commit comments

Comments
 (0)