[maennchen]

CI now creates the GitHub release in one gh release create call, after all assets exist. Immutable releases reject uploads after creation, so this order is necessary. The docs archive now has a build provenance attestation, which we attach to the release. We no longer build or attach package.tar. This matches oidcc.

The rest hardens CI the same way as oidcc. Actions are pinned to commit SHAs. Tokens are read-only by default and checkouts do not keep credentials. Every job runs harden-runner. Pull requests get dependency review, and Credo results go to code scanning. CodeQL, zizmor and OpenSSF Scorecard now check the workflows. Hex publishing uses workload identity, so we no longer need HEX_API_KEY.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.