Skip to content

sadr: upkeep 2026-11-15 - #10

Merged
sadrbot[bot] merged 1 commit into
mainfrom
sadr/upkeep
Nov 15, 2026
Merged

sadrbot[bot] merged 1 commit into
mainfrom
sadr/upkeep

Conversation

@sadrbot

@sadrbot sadrbot Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

What this PR does

Sadr moved the Semgrep CI image from 1.183.0 to 1.184.0, the newest tag whose digest has cleared the 7-day cooldown. Every other pin, the Node runtime and the koreader/test-data commit already meet the standard.

Changes

  • CI: semgrep/semgrep 1.183.0 → 1.184.0, pinned by digest sha256:cc1b6826… (.github/workflows/semgrep.yml)

Supply chain

  • cooldown: unchanged (the repo has no package manager and no lockfile)
  • pins: semgrep/semgrep:1.184.0@sha256:cc1b68266f267878b39739373ea9985b9a78e5d64497dd875c8de100b22695ed (built 2026-11-05T18:52Z). actions/checkout v7.0.1, actions/setup-node v7.1.0, actions/upload-artifact v7.0.2 and koreader/kosync:latest are already on their newest releases past the cooldown.
  • cooldown exceptions: none
  • inside the cooldown (already merged): none
  • waiting for cooldown: semgrep/semgrep 1.185.0 (clears 2026-11-17T09:04Z) | Node 26.13.1, a security release (clears 2026-11-18T16:44Z)

Security findings

  • untriaged: 0 → 0 (Semgrep API and semgrep ci --dry-run)
  • open: 0 → 0
  • fixed: 0
  • false positive: 0
  • accepted risk: 0
  • other: 0
  • suppressions reviewed: 0

Holds

  • None.

AGENTS.md

  • None.

Merging

  • auto-merge: all (owner Settings in pid1/.github, upkeep PRs)
  • turned on auto-merge (merge)

Needs you

  • None.

Verification

  • node 26.13.0 (the CI version) --check on verify.mjs, vectors/check.mjs and coverage.mjs: all three parse
  • node coverage.mjs: "OK — spec and verifier agree."
  • node vectors/check.mjs --big --koreader koreader-test-data: 10 passed, 0 failed, against koreader/test-data at c3b5d06e1ae8ea088bd898b0e7f9da3753d0d86c
  • node verify.mjs --help: exits 2, as designed
  • reference check against koreader/kosync:latest@sha256:bb3f1361… started with sh reference-server/run.sh start (KOSYNC_NAME=kosync-sadr-upkeep, KOSYNC_PORT=18081), with ciuser2 registered as in the reference job: "RESULT: conformant (every MUST satisfied)", exit 0. Sadr stopped the server after the check.
  • The checks above ran on main (215501b) before the change and again on the branch. All passed both times.
  • docker run semgrep/semgrep:1.184.0@sha256:cc1b6826… semgrep --version: 1.184.0
  • semgrep ci --dry-run on main and on the branch: 3 code findings each, all 3 triaged as accepted risk on the platform. Products: Code and Supply Chain.
  • pins.py check .github/workflows/*.yml: 13 pins checked, 0 with problems
  • gitleaks 8.30.1 on the branch commits and on the full history of main: no leaks found

Run

  • 11 minutes, US$2.44 (the session's reported spend for this repo, coordinator included)

Not done or not checked

  • Node 26.13.1 is a security release inside the cooldown. Its advisories cover HTTP/2 and TLS servers, the https Agent and the permission model. CI runs the verifier as a plain-HTTP client against a local container, so Sadr did not add a cooldown exception. A later run moves CI to 26.13.1.
  • koreader/test-data has no release tags, so its pinned commit c3b5d06 stays. That commit is still the repo's default branch head.

Opened by Sadr, a dark factory for software.

1.184.0 is the newest semgrep/semgrep tag whose digest is at least 7 days old (built 2026-11-05T18:52Z). 1.185.0 clears the cooldown at 2026-11-17T09:04Z.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sadrbot
sadrbot Bot enabled auto-merge November 15, 2026 12:39
@sadrbot
sadrbot Bot merged commit 934bf6b into main Nov 15, 2026
4 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.

0 participants