From 63d65ba6bffad6e6177f389eb3044093bbfc6bec Mon Sep 17 00:00:00 2001 From: Renat Galimov Date: Fri, 30 Oct 2026 05:39:02 +0300 Subject: [PATCH 1/2] chore: use renamed sbomify/sbomify-action --- .github/workflows/sbom.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/sbom.yml b/.github/workflows/sbom.yml index 6d50ee98..b31c124c 100644 --- a/.github/workflows/sbom.yml +++ b/.github/workflows/sbom.yml @@ -17,7 +17,7 @@ jobs: - uses: actions/checkout@v4 - name: Upload SBOM - uses: sbomify/github-action@master + uses: sbomify/sbomify-action@master env: TOKEN: ${{ secrets.SBOMIFY_TOKEN }} COMPONENT_ID: 'UUzAdk8ixV' From 69d568d2502961b9ea679a48bbce51d7ef42b86a Mon Sep 17 00:00:00 2001 From: Renat Galimov Date: Thu, 12 Nov 2026 19:45:51 +0000 Subject: [PATCH 2/2] ci(sbom): pin sbomify-action image by digest (26.11.0) The action's action.yml runs ghcr.io/sbomify/sbomify-action:latest, so a branch or commit-SHA ref still executes whatever image :latest points to. Reference the 26.11.0 image digest directly, as Screenly and Qt-Snap already do. --- .github/workflows/sbom.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/sbom.yml b/.github/workflows/sbom.yml index b31c124c..ca89ab9e 100644 --- a/.github/workflows/sbom.yml +++ b/.github/workflows/sbom.yml @@ -17,7 +17,10 @@ jobs: - uses: actions/checkout@v4 - name: Upload SBOM - uses: sbomify/sbomify-action@master + # Image digest, not a repo ref: the action's action.yml runs + # ghcr.io/sbomify/sbomify-action:latest, so even a commit-SHA pin + # would execute whatever image :latest points to at run time. + uses: docker://ghcr.io/sbomify/sbomify-action@sha256:376e319b46134efc0b158bb5eae76a8a6b988864fd6b0a02d506ca798a238d48 # 26.11.0 env: TOKEN: ${{ secrets.SBOMIFY_TOKEN }} COMPONENT_ID: 'UUzAdk8ixV'