From 6667ff405e229e5035cdbf71c51e843bf682c227 Mon Sep 17 00:00:00 2001 From: Brian Ojeda <9335829+sgtoj@users.noreply.github.com> Date: Mon, 9 Nov 2026 13:22:20 -0500 Subject: [PATCH 1/4] ci(deps): bump amannn/action-semantic-pull-request from 6.1.1 to 6.1.2 6.1.2 was released 4 days ago, inside the 5-day wait for new releases, but it fixes known vulnerabilities in the code the action bundles. 6.1.1 bundles @fastify/busboy 2.1.1 (GHSA-gxm5-99cw-xjw9, CRLF injection; GHSA-x8mw-p69m-v3mx, denial of service), which 6.1.2 drops, and undici 5.29.0, which 6.1.2 updates to 6.24.1, fixing GHSA-2mjp-6q6p-2qxm (request smuggling), GHSA-4992-7rv2-5pvq (CRLF injection), GHSA-g9mf-h72j-4rw9, GHSA-v9p9-hfj2-hcw8, and GHSA-vrm6-8vpv-qv8q. undici 6.24.1 still has open advisories, and no release of the action bundles a newer undici yet. The action only calls the GitHub API, with the workflow's read-only token. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/semantic-check.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/semantic-check.yaml b/.github/workflows/semantic-check.yaml index 2e76a01..7de9607 100644 --- a/.github/workflows/semantic-check.yaml +++ b/.github/workflows/semantic-check.yaml @@ -15,7 +15,7 @@ jobs: name: Semantic Commit Message Check runs-on: ubuntu-latest steps: - - uses: amannn/action-semantic-pull-request@48f256284bd46cdaab1048c3721360e808335d50 # v6.1.1 + - uses: amannn/action-semantic-pull-request@2252a14e810aa9b85c2d560bd7070c802206ecf6 # v6.1.2 name: Check PR for Semantic Commit Message env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} From b7ddf3e2299a5df5277171660917d6e851438133 Mon Sep 17 00:00:00 2001 From: Brian Ojeda <9335829+sgtoj@users.noreply.github.com> Date: Mon, 9 Nov 2026 13:22:20 -0500 Subject: [PATCH 2/4] chore(deps): bump the compose demo's curl image from 8.12.1 to 8.23.0 Dependabot watched only the Dockerfile, so the image the demo sends reports with was still the release from February 2025. Co-Authored-By: Claude Opus 5.5 --- docker-compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker-compose.yml b/docker-compose.yml index 27376ab..702e3f2 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -19,7 +19,7 @@ services: # sends the example reports in both formats, once the api is healthy demo-sender: - image: curlimages/curl:8.12.1 + image: curlimages/curl:8.23.0 depends_on: api: condition: service_healthy From f1c58fea0d0f5686124059e85e765ca17b92af96 Mon Sep 17 00:00:00 2001 From: Brian Ojeda <9335829+sgtoj@users.noreply.github.com> Date: Mon, 9 Nov 2026 13:25:29 -0500 Subject: [PATCH 3/4] chore(deps): base the dev container on debian trixie Debian 13 (trixie) is the current stable release, and bookworm is now oldstable, covered only by long-term support. The docker-outside-of-docker feature installs Moby by default, which fails on trixie because Debian 13 doesn't package moby-cli. With moby set to false it installs Docker CE's CLI and Compose plugin instead, which talk to the host's daemon the same way. Co-Authored-By: Claude Opus 5.5 --- .devcontainer/devcontainer.json | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json index 8c4d728..38bf1e2 100644 --- a/.devcontainer/devcontainer.json +++ b/.devcontainer/devcontainer.json @@ -1,11 +1,13 @@ { "name": "browser-reporting-api", - "image": "mcr.microsoft.com/devcontainers/base:bookworm", + "image": "mcr.microsoft.com/devcontainers/base:trixie", "features": { "ghcr.io/devcontainers/features/go:1": { "version": "1.27" }, - "ghcr.io/devcontainers/features/docker-outside-of-docker:1": {} + "ghcr.io/devcontainers/features/docker-outside-of-docker:1": { + "moby": false + } }, "forwardPorts": [8080], "postCreateCommand": "go mod download", From b81a8427ec1630ebda3f944e1f74bdfa40f55dc4 Mon Sep 17 00:00:00 2001 From: Brian Ojeda <9335829+sgtoj@users.noreply.github.com> Date: Mon, 9 Nov 2026 13:25:29 -0500 Subject: [PATCH 4/4] ci: wait 5 days before dependabot proposes a new release Version updates now wait until a release is 5 days old, so a broken or compromised release is more likely to be caught and pulled before it is proposed. Without a cooldown, Dependabot proposed releases within hours. Cooldown doesn't apply to security updates, which still arrive right away. Dependabot also watches docker-compose.yml. It read only the Dockerfile, so the demo's curl image went unchecked. CONTRIBUTING describes the rule, so manual updates follow it too. Co-Authored-By: Claude Opus 5.5 --- .github/dependabot.yaml | 21 +++++++++++++++++++++ CONTRIBUTING.md | 10 ++++++++++ 2 files changed, 31 insertions(+) diff --git a/.github/dependabot.yaml b/.github/dependabot.yaml index 4bd58b6..8326159 100644 --- a/.github/dependabot.yaml +++ b/.github/dependabot.yaml @@ -1,9 +1,15 @@ version: 2 + +# Version updates wait until a release is 5 days old, so a broken or +# compromised release is more likely to be caught before it is proposed. +# Security updates aren't delayed. updates: - package-ecosystem: "github-actions" directory: "/" schedule: interval: "weekly" + cooldown: + default-days: 5 groups: github-actions: patterns: ["*"] @@ -12,6 +18,8 @@ updates: directory: "/" schedule: interval: "weekly" + cooldown: + default-days: 5 groups: go-modules: patterns: ["*"] @@ -21,6 +29,19 @@ updates: directory: "/" schedule: interval: "weekly" + cooldown: + default-days: 5 groups: docker: patterns: ["*"] + + # images in docker-compose.yml + - package-ecosystem: "docker-compose" + directory: "/" + schedule: + interval: "weekly" + cooldown: + default-days: 5 + groups: + docker-compose: + patterns: ["*"] diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c450ae4..01574c3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -53,6 +53,16 @@ Docker Compose, with the settings in `.env` (copy `.env.example`). - Error responses are seen by clients. Return a generic message for server errors, and log the details. +## Dependencies + +Dependabot proposes updates to Go modules, GitHub Actions, and the images in +the Dockerfile and `docker-compose.yml` every week. It waits until a release +is 5 days old, so a broken or compromised release is more likely to be caught +first, but it doesn't delay security updates. Follow the same rule when +updating by hand: take a release younger than 5 days only when it fixes a +known vulnerability. Actions are pinned to a full commit SHA, with the +version in a comment. + ## Commits and releases Pull request titles follow [Conventional Commits](https://www.conventionalcommits.org/)