CI: pull fresh base images, so a security release is never held back by the runner's cache
ci / client (pull_request) Successful in 23s
ci / lint (pull_request) Successful in 9s
ci / server (mysql) (pull_request) Successful in 13s
ci / server (sqlite) (pull_request) Successful in 14s
ci / sidecar (pull_request) Successful in 25s
ci / nox (pull_request) Successful in 56s
ci / image (pull_request) Successful in 3m19s
ci / sourcemaps (pull_request) Skipped
ci / deploy (pull_request) Skipped

The 2026-10-21 Node.js security release (critical RCE, fixed in 22.23.4)
reached production only after a rebuild with a fresh base image: the
mac1 and mac2 runners still held node:22 from 2+ weeks before. docker
build now uses --pull, and workflow_dispatch allows a rebuild without a
code change. Merging this rebuilds and redeploys on Node 22.23.4.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Paul Hitt
2026-10-23 07:58:09 -04:00
co-authored by Claude Opus 5.5
parent a5f53e8886
commit 26f2f38cb2
+3 -2
View File
@@ -14,6 +14,7 @@
name: ci
on:
workflow_dispatch:
push:
branches: [main]
pull_request:
@@ -89,8 +90,8 @@ jobs:
- name: build
run: |
T=${GITHUB_SHA::8}
docker build -t "$IMAGE:$T" -t "$IMAGE:latest" .
docker build -t "$REDUCE_IMAGE:$T" -t "$REDUCE_IMAGE:latest" ./sidecar
docker build --pull -t "$IMAGE:$T" -t "$IMAGE:latest" .
docker build --pull -t "$REDUCE_IMAGE:$T" -t "$REDUCE_IMAGE:latest" ./sidecar
- name: hadolint
run: docker run --rm -i hadolint/hadolint hadolint --no-color --failure-threshold warning --ignore DL3003 --ignore DL3059 - < Dockerfile
- name: smoke test (sqlite boot, dummy secrets)