Compare commits

...

2 Commits

Author SHA1 Message Date
Brian DeHamer
a2bbfa2537 bump actions/attest from 4.0.0 to 4.1.0 (#838)
Signed-off-by: Brian DeHamer <bdehamer@github.com>
2026-02-26 15:02:14 -08:00
Brian DeHamer
0856891a35 update RELEASE.md docs (#836)
Signed-off-by: Brian DeHamer <bdehamer@github.com>
2026-02-25 16:02:48 -08:00
2 changed files with 1 additions and 20 deletions

View File

@@ -3,25 +3,6 @@
Follow the steps below to tag a new release for the
`actions/attest-build-provenance` action.
If changes were made to the internal `actions/attest-build-provenance/predicate`
action (any updates to [`./predicate/action.yaml`](./predicate/action.yml) or
any of the code in the [`./src`](./src) directory), start with step #1;
otherwise, skip directly to step #5.
1. Merge the latest changes to the `main` branch.
1. Create and push a new predicate tag of the form `predicate@X.X.X` following
SemVer conventions:
```shell
git tag -a "predicate@X.X.X" -m "predicate@X.X.X Release"
git push --tags
```
1. Update the reference to the `actions/attest-build-provenance/predicate`
action in [`action.yml`](./action.yml) to point to the SHA of the newly
created tag.
1. Push the `action.yml` change and open a PR. Once it has been reviewed, merge
the PR and proceed with the release instructions.
1. Create a new release for the top-level action using a tag of the form
`vX.X.X` following SemVer conventions:

View File

@@ -92,7 +92,7 @@ runs:
id: attest
env:
NODE_OPTIONS: "--max-http-header-size=32768"
uses: actions/attest@c32b4b8b198b65d0bd9d63490e847ff7b53989d4 # v4.0.0
uses: actions/attest@59d89421af93a897026c735860bf21b6eb4f7b26 # v4.1.0
with:
subject-path: ${{ inputs.subject-path }}
subject-name: ${{ inputs.subject-name }}