From f18f83ae6b31ffd1dc246df4388219966d5752e5 Mon Sep 17 00:00:00 2001 From: Brian DeHamer Date: Wed, 25 Feb 2026 16:02:29 -0800 Subject: [PATCH] update RELEASE.md docs (#254) Signed-off-by: Brian DeHamer --- RELEASE.md | 18 ------------------ 1 file changed, 18 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index cc11b39..a2df4ec 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -3,24 +3,6 @@ Follow the steps below to tag a new release for the `actions/attest-sbom` action. -If changes were made to the internal `actions/attest-sbom/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-sbom/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: