@@ -33,3 +33,30 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
3333 carrying a ` drift-detection ` label when ` has-changes == 'true' ` , instead
3434 of filing a new Issue every run. See the README's "Drift detection"
3535 section.
36+ - ` .github/dependabot.yml ` : weekly ` github-actions ` update checks,
37+ covering every pinned SHA in ` action.yml ` and the workflow files.
38+ - ` SECURITY.md ` : documents the SHA-pinning verification practice and
39+ points to GitHub's private vulnerability reporting as the disclosure
40+ channel.
41+ - ` .github/workflows/release.yml ` : on a ` v* ` tag push, archives the
42+ tagged tree and attests it with ` actions/attest-build-provenance ` ,
43+ then creates a GitHub Release from that archive. See the README's
44+ "Supply chain" section for exactly what the attestation does and does
45+ not prove.
46+ - README "Supply chain" section: Dependabot cadence, the ` SECURITY.md `
47+ link, the release attestation's scope and limits, and a manual
48+ follow-up note to enable tag protection on ` v* ` once ` v1 ` is tagged.
49+
50+ ### Notes
51+
52+ - ` v1 ` hasn't been tagged yet. Before it is, a few things still need a
53+ real, live run rather than a static check: a plan/apply against a real
54+ R2 bucket and a real S3 bucket, a ` policy-command ` failure proven to
55+ block a real ` apply ` (not just a step that reports failure), and a
56+ real tag push exercised through ` release.yml ` end to end. Once ` v1 `
57+ exists, tag protection on ` v* ` also needs to be enabled by hand in the
58+ repo's Settings, see the README's "Supply chain" section.
59+ - Private vulnerability reporting (Settings -> Security -> Private
60+ vulnerability reporting) needs enabling by hand too. ` SECURITY.md `
61+ documents it as the disclosure channel, but the toggle isn't on by
62+ default, so it needs confirming before that channel actually exists.
0 commit comments