ESPSomfy-RTS/.github/workflows
cjkas 5c57d1a2cd ci: signed release provenance, pinned dependencies, security scanning
- Release files get a SHA256SUMS file and a Sigstore-signed build
  provenance attestation (gh attestation verify).
- The workflows read the repo only. A new release job, which runs no
  build tools, is the only one that can write: it uploads the files with
  gh and pushes the version bump. The third-party release actions are gone.
- Every action is pinned to a commit SHA, esptool and the libraries to
  exact versions. The release tag reaches the shell through env, and
  set_version.sh rejects tags that aren't versions.
- New workflows: CodeQL (C++ via the native build, JS, Python, Actions),
  OpenSSF Scorecard, zizmor. Dependabot moves the action pins.
- SECURITY.md: private reporting, checking a download. README badges.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 13:27:48 +01:00
..
build.yaml ci: signed release provenance, pinned dependencies, security scanning 2026-10-31 13:27:48 +01:00
codeql.yml ci: signed release provenance, pinned dependencies, security scanning 2026-10-31 13:27:48 +01:00
scorecard.yml ci: signed release provenance, pinned dependencies, security scanning 2026-10-31 13:27:48 +01:00
zizmor.yml ci: signed release provenance, pinned dependencies, security scanning 2026-10-31 13:27:48 +01:00