Skip to content

DOMFortify 1.0.1

DOMFortify 1.0.1 #7

Workflow file for this run

name: Sign Release
on:
release:
types: [published]
permissions:
contents: read
jobs:
sign:
runs-on: ubuntu-latest
permissions:
contents: write # to attach .sigstore bundles to the release
id-token: write # OIDC for keyless signing
steps:
- uses: step-security/harden-runner@05e31511f85b41b11d1cf0ef85d0992719546e2c # v2.21.0
with:
egress-policy: audit
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
ref: ${{ github.event.release.tag_name }}
persist-credentials: false
# Build the tagged release's dist so we sign exactly what was released
# (and the same bytes slsa-provenance attests), not stale committed dist
# from whatever branch the workflow happened to check out.
- uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
with:
node-version: 22
- run: npm ci --ignore-scripts
- run: npm run build
- uses: sigstore/gh-action-sigstore-python@790bc6befb9d733738f18d8f895854b453640ec9 # v3.0.1
with:
inputs: dist/fortify.min.js dist/fortify.js
# Re-uploads signed artefacts to the release that triggered this run.
# Without this flag, .sigstore bundles are generated but dropped at
# job end - the release page gets nothing.
release-signing-artifacts: true