Skip to content

Supply chain: pinned actions and images, Dependabot, image SBOM and scan, docs - #22

Merged
AlxcBTW merged 2 commits into
mainfrom
chore/supply-chain
Oct 24, 2026
Merged

AlxcBTW merged 2 commits into
mainfrom
chore/supply-chain

Conversation

@AlxcBTW

@AlxcBTW AlxcBTW commented Oct 24, 2026

Copy link
Copy Markdown
Member

Supply-chain hardening of the CI around the network.

  • Every third-party action pinned by full commit SHA with a # vX.Y.Z comment (SHAs looked up from the release tags with gh api).
  • persist-credentials: false on every checkout; workflows keep contents: read.
  • .github/dependabot.yml: weekly, grouped updates for actions and for crates (workspace and fuzz/), with a 7-day cooldown.
  • cargo-deny already runs on every PR through the shared rules workflow; advisories.yml runs the same check every Monday, because advisories appear without commits. cargo deny --all-features check is clean locally.
  • docs/supply-chain.md: what is pinned, how updates arrive, what is not covered (signing, reproducible builds).

No Rust files changed. fmt, clippy and tests pass locally; actionlint is clean.

Cloud specific:

  • Base images of deploy/Dockerfile and the service/test images of the workflows are pinned by index digest, with the tag in a comment; Dependabot's docker entry moves both.
  • The docker job now writes a CycloneDX SBOM per image (artifact image-reports) and a Trivy report (fixable HIGH/CRITICAL) into the job summary. Trivy 0.75.0 is downloaded and checked against its SHA-256. It does not block: the baseline of the images is unknown, and a new Debian CVE would turn unrelated PRs red. How to make it blocking is in docs/supply-chain.md.
  • No workflow pushes an image, so there is nothing to attach provenance to; the doc says what to add when one does.

@AlxcBTW
AlxcBTW merged commit 49ce409 into main Oct 24, 2026
9 checks passed
@AlxcBTW
AlxcBTW deleted the chore/supply-chain branch October 24, 2026 14:37
AlxcBTW added a commit that referenced this pull request Oct 24, 2026
* Party voice: members announce their endpoint

Store endpoint, relay and voice per party member (migration 0009) and add
PUT /v1/party/endpoint. The three go out in every Party, never in a
PartyInvitation, and go away with the member's row when it leaves, is
removed or the party ends. An unchanged announcement keeps the revision
and sends no event. Needs network #22 (PartyMember fields, PartyEndpoint,
the net service's audio config used by the e2e tests).

* Lock the network's voice crate; tidy the endpoint update
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