Skip to content

feat: add dependabot, security policy, and release attestation - #6

Merged
igorjs merged 4 commits into
mainfrom
feat/enterprise-hardening-s6-provenance
Sep 7, 2026
Merged

igorjs merged 4 commits into
mainfrom
feat/enterprise-hardening-s6-provenance

Conversation

@igorjs

@igorjs igorjs commented Sep 4, 2026

Copy link
Copy Markdown
Member

Summary

Pinned actions can drift silently with no automated check, there was no clear channel for reporting a vulnerability, and a tagged release had no way to prove what actually produced it. This closes that gap: dependency updates, a disclosure path, and a release attestation.

What Changed

  • Add .github/dependabot.yml, weekly github-actions ecosystem checks covering the pinned SHAs in both action.yml and the workflow files.
  • Add SECURITY.md, documents how to verify a SHA pin against its tag yourself and points to GitHub's private vulnerability reporting for disclosures. No email address anywhere, reports go through GitHub only.
  • Add .github/workflows/release.yml, triggers on a v* tag push, archives the tagged tree, attests it with actions/attest-build-provenance, and creates a GitHub Release from that archive.
  • Document in the README and CHANGELOG exactly what the attestation proves and doesn't: it's a real guarantee the archive came from this workflow run, but it's thinner than a build-provenance chain for a compiled artifact, since this repo doesn't produce one.

Notes for reviewers

  • One manual step is still needed after merge: once v1 is tagged, enable tag protection on v* in the repo's Settings (Rulesets or tag protection). No workflow or Terraform can do this, it's a Settings change.
  • release.yml hasn't been exercised against a real tag yet. Before tagging the real v1, push a throwaway pre-release tag like v0.0.0-test to confirm the archive, attestation, and release creation work end to end, then delete it.
  • This is the sixth and last PR in the enterprise-hardening stack (feat: support S3 backend, safer command default, self-lint CI #1 through feat(drift-detection): add scheduled example with sticky issue #5 are the other five). Together they form the complete plan. A few non-blocking items from the post-implementation review are still open: the apply-time policy check runs inline instead of as its own step, tests/action-logic.sh bundles four unrelated test concerns into one file, boundary test coverage is asymmetric between the r2 and s3 credential checks, and there are a handful of lower-priority test-assertion-strength gaps. None of these block the stack, they're tracked as follow-ups.

Related work

@igorjs
igorjs force-pushed the feat/enterprise-hardening-s5-drift-detection branch 2 times, most recently from b01dd29 to 2abfd46 Compare September 7, 2026 04:27
Signed-off-by: igorjs <2278164+igorjs@users.noreply.github.com>
Signed-off-by: igorjs <2278164+igorjs@users.noreply.github.com>
On a version tag push, archive the tagged tree with git archive, attest
it via actions/attest-build-provenance, then create a GitHub Release
with the archive attached.

Deviations from the WU-13 brief found during verification:
- actions/checkout needs no with: overrides. actions/checkout fetches
  the exact ref that triggered the workflow by default, and on a
  push: tags: trigger that ref is refs/tags/<tag> itself, so the tag
  is already resolvable locally for git archive without fetch-depth: 0
  or fetch-tags: true. Verified against actions/checkout v7.0.1 source
  (ref-helper.ts, input-helper.ts) and README.
- Added artifact-metadata: write to the job permissions. attest-build-provenance
  v4.2.2 wraps actions/attest@v4.2.1 internally, whose own README lists
  id-token: write, attestations: write, and artifact-metadata: write as
  the permissions to set, a set the brief's list was missing one of.

Signed-off-by: igorjs <2278164+igorjs@users.noreply.github.com>
@igorjs
igorjs force-pushed the feat/enterprise-hardening-s6-provenance branch from 3a7b1df to d06111b Compare September 7, 2026 04:28
@igorjs
igorjs changed the base branch from feat/enterprise-hardening-s5-drift-detection to main September 7, 2026 04:28
Add Supply chain README section covering Dependabot cadence, the
SECURITY.md link, and the release attestation's scope and limits.
Document the manual tag-protection follow-up for v1 in README and
CHANGELOG. Add matching CHANGELOG entries for dependabot, SECURITY.md,
and the release workflow.

Remove the unused artifact-metadata: write permission from
release.yml: push-to-registry stays unset and the permission was
never exercised, resolving the self-contradiction the prior pass's
own comment already admitted.

Add enabling GitHub's private vulnerability reporting to the pre-v1
manual checklist in CHANGELOG, since SECURITY.md documents it as the
disclosure channel but the toggle isn't on by default.

Signed-off-by: igorjs <2278164+igorjs@users.noreply.github.com>
@igorjs
igorjs force-pushed the feat/enterprise-hardening-s6-provenance branch from d06111b to f27ae4e Compare September 7, 2026 05:01
@igorjs
igorjs marked this pull request as ready for review September 7, 2026 05:02
@igorjs
igorjs merged commit 41dde5d into main Sep 7, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant