Skip to content

Update dockerfile dependencies - #5006

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/dockerfile
Nov 6, 2026
Merged

renovate[bot] merged 1 commit into
mainfrom
renovate/dockerfile

Conversation

@renovate

@renovate renovate Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
alpine (source) final digest 294b683 → be26560
golang (source) stage digest 8a5910f → d200d2d
node (source) final patch 24.22.1-alpine → 24.22.2-alpine

Release Notes

nodejs/node (node)

v24.22.2: 2026-10-28, Version 24.22.2 'Krypton' (LTS), @​aduh95

Compare Source

Commits

Configuration

📅 Schedule: (in timezone Etc/UTC)

  • Branch creation
    • "after 5pm on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Nov 2, 2026
@renovate
renovate Bot requested a review from a team as a code owner November 2, 2026 18:51
@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Nov 2, 2026
@renovate
renovate Bot enabled auto-merge (squash) November 2, 2026 18:51
@claude

claude Bot commented Nov 2, 2026

Copy link
Copy Markdown

Reviewed this Renovate digest bump — looks clean, no findings.

What changed: alpine:3.24 digest 294b683 → be26560 in stacks/flow.Dockerfile:33 and stacks/peerdb-server.Dockerfile:44. Nothing else in the diff.

Verification:

  • Confirmed against Docker Hub that be2656061b536c1883c4034790e21d0a09c5aaaf51968b89368a3c0371ea2c9a is the current manifest-list digest for both alpine:3.24 and alpine:3.24.3 (published 2026-10-23). The old digest 294b683… is alpine:3.24.2. So this is a 3.24.2 → 3.24.3 patch move within the same stable branch — no minor/major jump, no musl ABI change.
  • Upstream release notes for 3.24.3 (released 2026-10-21, alongside 3.21.9/3.22.7/3.23.7) list security fixes only: ca-certificates (eMudhra intermediate CA distrust), musl (CVE-2026-107891), OpenSSL (CVE-2026-35189, -42772, -54872/3/5, -72897, -75804/5/6, -77696, -84782, -84784), zlib (CVE-2026-85091), and PHP 8.3–8.5 (not installed in these images). No behavioral or packaging changes that would affect the runtime images.
  • Both alpine:3.24 references in the repo were updated consistently; grep for the old digest returns no remaining occurrences. The builder stages (golang:1.27-alpine, cargo-chef:latest-rust-1.99.1-alpine) are pinned separately and untouched, which is fine for a patch-level musl bump.
  • No logging/output changes, so no PII or secret-exposure surface.

Minor note (informational, not blocking): the ca-certificates update removes trust in a compromised eMudhra intermediate CA. This only matters if a peer or destination endpoint presents a certificate chaining through that CA — an intentional upstream distrust, not a regression.

@claude

claude Bot commented Nov 2, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

Details: This PR is a same-tag digest refresh of the pinned alpine:3.24 base image (sha256:294b683… → sha256:be26560…) in stacks/flow.Dockerfile and stacks/peerdb-server.Dockerfile. Both files were updated consistently, the flow-base stage alias is preserved, and no other references to the old digest remain in the repo.

Dependency regression check (REVIEW.md): Alpine same-tag digest bumps correspond to routine stable-branch rebuilds (backported security/bugfix package updates only), which is the lowest-risk category of Renovate update. Note: the review environment had no outbound network access to Docker Hub or the Alpine upstream repos, so the specific point-release changelog for this digest range could not be independently verified.

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from c6d722c to 75e1cc5 Compare November 2, 2026 20:00
@renovate renovate Bot changed the title chore(deps): update alpine:3.24 docker digest to be26560 Update alpine:3.24 Docker digest to be26560 Nov 2, 2026
@claude

claude Bot commented Nov 2, 2026

Copy link
Copy Markdown

Renovate review — reviewed, looks clean ✅

Change: alpine:3.24 digest 294b683 → be26560 in stacks/flow.Dockerfile:33 and stacks/peerdb-server.Dockerfile:44. Digest-only bump, tag stays 3.24.

Verification

  • The new digest matches the multi-arch index currently published for library/alpine:3.24 on Docker Hub (last updated 2026-10-23), covering amd64/arm64 among others — so this is the real upstream tag, not a stale or mismatched pin.
  • Both Dockerfiles were updated consistently; grep confirms no other reference to the old digest remains in the repo.
  • docker-build / docker-build-external checks are green.

Upstream changes in range
The bump corresponds to docker-alpine v3.24 → Alpine 3.24.3 (2026-10-21), a patch release that is security fixes only — no breaking changes announced:

  • musl — CVE-2026-107891 (ABI unchanged)
  • zlib — CVE-2026-85091
  • openssl — CVE-2026-35189, -42772, -54872, -54873, -54875, -72897, -75804, -75805, -75806, -77696, -84782, -84784
  • ca-certificates — updated for the eMudhra intermediate CA compromise
  • php — CVE-2026-109618, -109619 (not installed in either image)

Alpine also confirmed that aports, packages, and the Oct 21 releases were not tampered with during their GitLab incident.

Regression risk
Low. The only behavioural change worth noting is the ca-certificates trust-store update: the eMudhra intermediate is now distrusted, so a peer whose TLS chain terminates at that CA would start failing verification. That is the intended security outcome rather than a regression, and in practice both images run apk add --no-cache ca-certificates at build time anyway, so the trust store already tracked current apk content independently of the base digest. The AWS RDS global bundle added in flow.Dockerfile is pinned by its own checksum and is unaffected.

No PII/secret exposure, no new stdout/stderr/log output, no API or build-arg surface changes. Nothing blocking.

@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: Infrastructure flake: the cockroachdb-v25_ch-stable job failed during Docker service bring-up because host port 40002 was already in use when starting flow-snapshot-worker (all 3 recovery attempts hit the same bind error), so no tests ever ran, while all 18 other matrix jobs on the same commit passed.
Confidence: 0.95

✅ Automatically retrying the workflow

View workflow run

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from 75e1cc5 to e1493fe Compare November 2, 2026 20:40
@claude

claude Bot commented Nov 2, 2026

Copy link
Copy Markdown

Renovate review — ✅ clean

Digest-only bump of alpine:3.24 in stacks/flow.Dockerfile:33 and stacks/peerdb-server.Dockerfile:44. Reviewed per .claude/REVIEW.md.

Digest verification

  • sha256:be2656061b536c1883c4034790e21d0a09c5aaaf51968b89368a3c0371ea2c9a is the current manifest-list digest for the 3.24 tag on Docker Hub (last pushed 2026-10-23), so the pin matches the tag it claims.
  • The index still carries both amd64 and arm64/v8 manifests, so the multi-arch builds are unaffected.
  • Both direct alpine:3.24 pins in the repo were bumped together — no stale digest left behind. Other alpine-flavoured bases (golang:1.27-alpine, node:24.22.1-alpine, cargo-chef:...-alpine, postgres:18-alpine) are tracked as separate deps and are out of scope here.

What changed upstream
The previous digest 294b683 was Alpine 3.24.2 (2026-09-17); the new one is Alpine 3.24.3 (upstream alpinelinux/docker-alpine commit 5aec467 "Update Alpine v3.24 - 3.24.3", 2026-10-21). This is a stable-branch patch release — security fixes only, no package major-version churn:

  • openssl — the 2026-09-29 advisory (CVE-2026-35189, -54872, -54873, -54875, -72897, -75804, -75805, -75806, -77696, -84782, -84784)
  • musl — CVE-2026-107891
  • zlib — CVE-2026-85091
  • ca-certificates — trust-store update for the eMudhra intermediate CA compromise
  • php 8.3–8.5 fixes (not installed in either image)

Regression assessment: none expected.

  • No ABI or major-version changes within the 3.24 branch, so geos, postgresql-client, curl and iputils installed via apk add --no-cache are unaffected. Those packages are unpinned anyway, so they already tracked the 3.24 repo state independently of the base digest.
  • The only behavioural change worth being aware of is the ca-certificates trust-store update: the distrusted eMudhra intermediate is removed. If any peer endpoint chained to it, TLS to that endpoint would now fail — but that is the intended security outcome, not a regression, and it is not something this repo depends on.
  • flow.Dockerfile adds the AWS RDS global bundle with an explicit --checksum=, so that trust material is pinned independently and unaffected by the base change.

No new stdout/stderr/log output and no credential handling in this diff, so the PII/secret-logging check is a no-op here.

🤖 Generated with Claude Code

@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: A single matrix job (maria-12_ch-stable) timed out after 3 minutes in the post-test cleanup wait ("wait for flow dropped") of TestApiMy/TestResyncWithSnapshotConfigOnRunningPipe, while the same 482-test package passed in every other MySQL/MariaDB job and the PR only bumps a Dockerfile base image — a timing-sensitive terminate-after-resync hang, not a regression from the change.
Confidence: 0.85

✅ Automatically retrying the workflow

View workflow run

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from e1493fe to 419d00e Compare November 3, 2026 02:02
@renovate renovate Bot changed the title Update alpine:3.24 Docker digest to be26560 Update dockerfile dependencies Nov 3, 2026
Comment thread stacks/flow.Dockerfile
# syntax=docker/dockerfile:1.28@sha256:bb22d9815c728170f72750f4e5b0d672e06176142e1d602c7e66c050100b7e5b

FROM golang:1.27-alpine@sha256:8a5910f31396cd4d89662f56c68b3ae31d374308270a1c3bd96672ee5ed43414 AS builder
FROM golang:1.27-alpine@sha256:d200d2dd76b03a99b52651fd1325aff7dcd35422c35c01bac56571b0507f3deb AS builder

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Release-note check (not a blocker) — this digest moves Go 1.27.2 → 1.27.3.

Digest d200d2d is exactly the current golang:1.27.3-alpine manifest list (pushed 2026-10-27); the previous 8a5910f was a 1.27.2 build. docker-library/golang bumped 1.27 → 1.27.3 on 2026-10-20.

Go 1.27.3 contains a single security fix, CVE-2026-111943 (golang/go#82345): crypto/x509.Verify now filters out any chain that passes through one of eight blocked intermediate CA keys, so such chains are no longer returned to the caller and verification fails.

Why this is worth a look for PeerDB specifically: the flow worker makes outbound TLS connections to user-supplied peers (Postgres, MySQL, MongoDB, Snowflake, ClickHouse, Kafka, Elasticsearch, S3). If any of those endpoints presents a chain through one of the blocked intermediates, it will start failing with a certificate-verification error once this image ships, and the upstream issue documents no GODEBUG opt-out. The CA is deliberately unnamed upstream, so this cannot be pre-verified from here — just something to recognize if peer TLS errors appear post-deploy, rather than diagnosing it as a PeerDB regression.

Otherwise the bump is clean: the tag is unchanged (1.27-alpine), flow/go.mod has no toolchain pin so it simply builds with 1.27.3, and no logging/stdout surface is touched.

Comment thread stacks/flow.Dockerfile
fi

FROM alpine:3.24@sha256:294b683cb724975bec92580e1e685676bd4b50bda910ddb8c51d4cabeaec77e6 AS flow-base
FROM alpine:3.24@sha256:be2656061b536c1883c4034790e21d0a09c5aaaf51968b89368a3c0371ea2c9a AS flow-base

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Release-note check (not a blocker) — this digest moves Alpine 3.24.2 → 3.24.3.

Digest be26560 is the current alpine:3.24 / alpine:3.24.3 manifest list (pushed 2026-10-23); 294b683 was 3.24.2 (2026-09-18). Per docker-library/official-images#22559, 3.24.3 is a pure security patch: musl, zlib and OpenSSL fixes plus ca-certificates refreshed to 20261020. No API/ABI breaks in an Alpine patch release.

The digest is applied consistently — both occurrences (here and stacks/peerdb-server.Dockerfile:44) were updated, and no stale alpine:3.24 pins remain anywhere in stacks/.

Minor note on the ca-certificates 20261020 refresh: line 36 does apk add --no-cache ca-certificates at build time, so the trust store already tracked the live 3.24 repo and is not actually gated by this digest pin. Same class of consideration as the Go 1.27.3 crypto/x509 change flagged on line 3.

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from 419d00e to cd2b786 Compare November 3, 2026 17:05
@claude

claude Bot commented Nov 3, 2026

Copy link
Copy Markdown

Review: dependency digest bump — looks clean ✅

Reviewed per .claude/REVIEW.md (Renovate dependency-bump checks). No findings.

What actually changed

Image Before After Upstream delta
golang:1.27-alpine 8a5910f = 1.27.1-alpine3.24 d200d2d = 1.27.3-alpine3.24 (2026-10-27) Go 1.27.1 → 1.27.3
alpine:3.24 294b683 = 3.24.2 be26560 = 3.24.3 (2026-10-23) Alpine 3.24.2 → 3.24.3

Digests verified against Docker Hub: both resolve to the tags they are pinned against (alpine:3.24/3.24.3/latest and golang:1.27-alpine/1.27.3-alpine3.24). Tags themselves are unchanged — digest-only bump, no major/minor jump.

Regression assessment

Go 1.27.1 → 1.27.3 (release history) — two patch releases, no language or API changes:

  • 1.27.3 (2026-10-19): security fix in crypto/x509 only — blocks 8 compromised eMudhra intermediate CA keys.
  • 1.27.2 (2026-10-08): security fixes in the go command, crypto/tls, html/template, net/http, net/textproto, os; plus bug fixes in the compiler, linker, runtime, vet, compress/flate, crypto/mlkem, encoding/json, encoding/json/v2, net/http, os.

Alpine 3.24.2 → 3.24.3 (release post) — patch release, security only: musl (CVE-2026-107891 — relevant since the flow binary is CGO-linked against musl), openssl (12 CVEs from the 2026-09-29 advisory), zlib (CVE-2026-85091), ca-certificates (same eMudhra intermediate CA revocation), php.

Only behavioral change worth being aware of: certificate chains relying on the revoked eMudhra intermediates will now fail verification — both in Go's crypto/x509 and in the image's ca-certificates. That is the intended fix, and it is very unlikely to affect PeerDB peer endpoints.

Consistency checks

  • Both alpine:3.24 pins (stacks/flow.Dockerfile:33, stacks/peerdb-server.Dockerfile:44) were updated to the same digest — no stale reference left anywhere in the repo.
  • The builder variant is still alpine3.24 (confirmed: 1.27-alpine == 1.27-alpine3.24; 1.27-alpine3.23 has a different digest), so it still matches the alpine:3.24 runtime base. This matters here because flow.Dockerfile builds with CGO_ENABLED=1 against geos-dev/musl-dev and links dynamically against the runtime image's geos/musl — an alpine-variant drift would be an ABI risk, and there is none.
  • Go 1.27.3 satisfies the go directives in flow/go.mod (1.26.0) and flow/pkg/go.mod (1.27.0); no toolchain directive to conflict with.
  • No logging/stdout/stderr changes, so no PII or secret-exposure surface in this diff.

🤖 Generated with Claude Code

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: Test_BigQuery_CDC_Isolated_Table_Backpressure_Does_Not_Block_Sibling hit a 2-minute WaitFor timeout waiting for BigQuery's APPENDS change feed to surface the first CDC batch, while the identical 59-test BigQuery suite passed in the bigquery_ch-stable and bigquery_ch-lts jobs of the same run — pointing to external-service latency rather than a code defect.
Confidence: 0.85

✅ Automatically retrying the workflow

View workflow run

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from cd2b786 to eb4b350 Compare November 3, 2026 18:48
Comment thread stacks/flow.Dockerfile
# syntax=docker/dockerfile:1.28@sha256:bb22d9815c728170f72750f4e5b0d672e06176142e1d602c7e66c050100b7e5b

FROM golang:1.27-alpine@sha256:8a5910f31396cd4d89662f56c68b3ae31d374308270a1c3bd96672ee5ed43414 AS builder
FROM golang:1.27-alpine@sha256:d200d2dd76b03a99b52651fd1325aff7dcd35422c35c01bac56571b0507f3deb AS builder

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a pure digest refresh — this moves the Go toolchain 1.27.1 → 1.27.3.

Upstream range (docker-library/golang commit log + Go release history):

  • Go 1.27.2 (2026-10-08) — 15 security backports: cmd/go toolchain and golang.org/fips140 checksum bypass via a malicious GOMODPROXY, crypto/tls, html/template XSS (stale jsCtx at template-literal entry; missing ES2015+ keywords in regexpPrecederKeywords), net/http (http2 transport accepting multiple Content-Length headers), net/textproto, os. Plus compiler, linker, runtime, compress/flate, encoding/json and encoding/json/v2 bug fixes.
  • Go 1.27.3 (2026-10-19) — crypto/x509 only (CVE-2026-111943 / GO-2026-6809). See the trust-store note on the alpine line below.

No API or behavioural change beyond the x509 denylist, so no regression risk I can see for flow. It also closes an existing drift: CI already pins go-version: 1.27.3 in ci.yml, flow.yml, golang-lint.yml, tilt-flow.yml and cleanup.yml, so until now the shipped binary was built with an older toolchain than the one tests ran against.

Comment thread stacks/flow.Dockerfile
fi

FROM alpine:3.24@sha256:294b683cb724975bec92580e1e685676bd4b50bda910ddb8c51d4cabeaec77e6 AS flow-base
FROM alpine:3.24@sha256:be2656061b536c1883c4034790e21d0a09c5aaaf51968b89368a3c0371ea2c9a AS flow-base

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alpine 3.24.2 → 3.24.3 (old 294b683… = 3.24.2, published 2026-09-18; new be26560… = 3.24.3, published 2026-10-23). Per docker-library/official-images#22559 this is a security point release: musl CVE-2026-107891, zlib CVE-2026-85091, 13 OpenSSL CVEs, and ca-certificates 20261020.

⚠️ One user-visible behavioural change — intended, not a bug, but worth a release note. ca-certificates 20261020 removes emSign Root CA - C1, emSign ECC Root CA - C3 and emSign ECC Root CA - G3 following the eMudhra intermediate key compromise, and the Go 1.27.3 crypto/x509 fix on line 3 adds a denylist for the affected intermediates. Combined, after this bump peer-flow will refuse TLS to any source/destination peer whose chain terminates in an emSign root, surfacing to users as x509: certificate signed by unknown authority. Narrow blast radius, but it is silent until runtime.

Three things I checked that are fine:

  • The known 3.24.3 breakage (ca-certificates-20261020-r0 conflicting with an exact ca-certificates=20260909-r0 pin) only hits Dockerfiles that pin the version. Both Dockerfiles here use unpinned apk add --no-cache ca-certificates, so no impact — consistent with docker-build passing.
  • The AWS RDS bundle added on line 35 is an Amazon root set with its own --checksum, unaffected by the emSign removal.
  • Builder and runtime move to the same Alpine 3.24.3 in this PR, so the CGO geos/musl link between the golang:1.27-alpine builder and this stage stays ABI-consistent. Both alpine:3.24 pins in the repo (here and peerdb-server.Dockerfile:44) were updated together.

cp target/${BUILD_MODE}/peerdb-server /root/target/

FROM alpine:3.24@sha256:294b683cb724975bec92580e1e685676bd4b50bda910ddb8c51d4cabeaec77e6
FROM alpine:3.24@sha256:be2656061b536c1883c4034790e21d0a09c5aaaf51968b89368a3c0371ea2c9a

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same 3.24.2 → 3.24.3 bump as flow.Dockerfile — correct and consistent.

Scope caveat on the 13 OpenSSL CVEs this release carries: the peerdb-server binary itself does not pick them up. The builder stage sets OPENSSL_STATIC=1 and installs openssl-libs-static (lines 13 and 15), so OpenSSL is statically linked from lukemathwalker/cargo-chef:latest-rust-1.99.1-alpine, whose digest this PR does not touch. The runtime bump does fix the OpenSSL used by postgresql-client and curl installed on line 46, and brings in the musl/zlib/ca-certificates fixes.

Pre-existing, not introduced here, and not a reason to hold this PR — but if the OpenSSL CVEs matter, the cargo-chef builder digest is the pin that actually needs to move.

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: Both failures are infrastructure, not test logic: postgres-18_other could not start flow-snapshot-worker because host port 40002 was "address already in use", and mysql-pos_ch-stable got an HTTP 500 downloading the Tilt tarball from GitHub releases — no tests ran in either job, and the other 9 matrix jobs passed on the same commit.
Confidence: 0.97

✅ Automatically retrying the workflow

View workflow run

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from eb4b350 to dafd925 Compare November 3, 2026 19:54
@claude

claude Bot commented Nov 3, 2026

Copy link
Copy Markdown

Re-reviewed per .claude/REVIEW.md on the current (unchanged) diff — still clean, no findings. Detailed analysis is in the earlier comment above; summary and one addition:

Image Before After
golang:1.27-alpine 8a5910f = 1.27.1-alpine3.24 d200d2d = 1.27.3-alpine3.24
alpine:3.24 294b683 = 3.24.2 be26560 = 3.24.3

Both digests re-verified against Docker Hub: they are the current digests for the tags they are pinned against, and 1.27-alpine still aliases alpine3.24 (not 3.23), so builder/runtime musl+geos ABI stays matched.

Upstream delta is security-only patch releases: Go 1.27.2 (15 CVEs, mostly net/http HTTP/2) and Go 1.27.3 (CVE-2026-111943, crypto/x509 rejects chains through 8 eMudhra emSign intermediates); Alpine 3.24.3 carries the matching ca-certificates revocation plus musl/openssl/zlib fixes. The only behavior change to be aware of is that peer endpoints whose chains pass through those eMudhra intermediates will now fail TLS verification — intended, and unlikely to affect real PeerDB peers.

Addition not in the earlier comment: this bump also closes a toolchain skew. Every CI workflow (ci.yml, flow.yml, golang-lint.yml, tilt-flow.yml, cleanup.yml) already pins go-version: 1.27.3, while the shipped image was still being built with 1.27.1. After this PR, CI and the release image build with the same Go patch release.

No stray copies of the old digests remain in the repo, and the diff adds no logging/stdout output, so there is no PII or secret-exposure surface.

🤖 Generated with Claude Code

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from dafd925 to a18978e Compare November 4, 2026 09:07
@claude

claude Bot commented Nov 4, 2026

Copy link
Copy Markdown

Renovate digest bump review — no findings

Reviewed per .claude/REVIEW.md. The diff is two base-image digest pins across three lines; no code, no new stdout/stderr/log output, so the PII/secret-leakage check is a trivial pass.

What the digests actually resolve to

Both new digests match what Docker Hub currently serves for the pinned tags (verified against the registry):

Image Before After
alpine:3.24 294b683 = 3.24.2 (2026-09-18) be26560 = 3.24.3 (2026-10-23)
golang:1.27-alpine 8a5910f = 1.27.1-alpine3.24 (2026-09-21) d200d2d = 1.27.3-alpine3.24 (2026-10-27)

So despite being a digest-only bump, this quietly moves the Go toolchain 1.27.1 -> 1.27.3. Worth knowing, since it is more than a rebuild.

Upstream changes in the bumped range

Alpine 3.24.2 -> 3.24.3 (release notes) is a security-only point release:

  • openssl: 11 CVEs from the 2026-09-29 advisory
  • musl: CVE-2026-107891
  • zlib: CVE-2026-85091
  • ca-certificates: eMudhra intermediate CA compromise
  • php: not installed in these images, irrelevant here

Go 1.27.1 -> 1.27.3 (release history):

  • 1.27.2 (2026-10-08): 15 security fixes across go, crypto/tls (KeyUpdate DoS), html/template (JS regexp context XSS), net/http (ReadHeaderTimeout now applied to the h2c preface read), net/textproto, os. It also fixes several 1.27.0/1.27.1 regressions: the multi-plugin stdlib-type corruption panic, a compiler bug, an encoding/json reflect.Value zero-value regression, and inflated go test coverage counting.
  • 1.27.3 (2026-10-19, URGENT track): crypto/x509 fix for CVE-2026-111943 / GO-2026-6809, distrusting eight compromised eMudhra intermediates during chain verification.

Regression assessment

No regressions found. Both patch ranges are security plus bugfix only; 1.27.2 in fact removes regressions rather than adding any. No breaking changes land inside the 1.27.x patch range (the compress/flate output change, GODEBUG removals, and stdversion check were all 1.27.0, already in use here). flow/go.mod declares go 1.27.0, satisfied by the newer toolchain.

I checked the one Go 1.27.2 change with plausible blast radius here, the net/http ReadHeaderTimeout/h2c-preface change: flow/cmd/api.go:158 serves the grpc-gateway over a plain http.Server with no h2c handler and a 5m ReadHeaderTimeout, so it is unaffected.

Operational note (not a blocker)

Both halves of this bump distrust the compromised eMudhra intermediates, Go via the crypto/x509 denylist and Alpine via ca-certificates. That is the intended fix, but it is a real behavior change for a replication engine that opens TLS connections to arbitrary customer databases: any source or destination whose chain goes through one of those intermediates will start failing verification after this lands. Nothing to change in the PR, just something to have an answer ready for.

Consistency check

All three pinned references in the repo were updated together (stacks/flow.Dockerfile:3, stacks/flow.Dockerfile:33, stacks/peerdb-server.Dockerfile:44); no stale copies of the old digests remain anywhere in the tree.

CI was still pending at review time, so this is a static review only. The tilt matrix should be green before automerge.

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from a18978e to 89f258b Compare November 4, 2026 10:18
@renovate renovate Bot changed the title Update dockerfile dependencies chore(deps): update dockerfile dependencies Nov 4, 2026
Comment thread stacks/flow.Dockerfile
# syntax=docker/dockerfile:1.28@sha256:bb22d9815c728170f72750f4e5b0d672e06176142e1d602c7e66c050100b7e5b

FROM golang:1.27-alpine@sha256:8a5910f31396cd4d89662f56c68b3ae31d374308270a1c3bd96672ee5ed43414 AS builder
FROM golang:1.27-alpine@sha256:d200d2dd76b03a99b52651fd1325aff7dcd35422c35c01bac56571b0507f3deb AS builder

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dep-bump review — golang:1.27-alpine 8a5910f → d200d2d is Go 1.27.1 → 1.27.3. The new digest is the current 1.27.3-alpine (identical to 1.27.3-alpine3.24). The old digest was pinned on 2026-09-30 in #4874, before 1.27.2 shipped, so this crosses two patch releases rather than one.

What the range contains:

⚠️ One behavioral change worth knowing about before merge, since it gets baked into the shipped flow binaries: go1.27.3 makes x509.Certificate.Verify filter out any chain containing one of eight blocklisted intermediate CA keys (the eMudhra intermediates Mozilla added to OneCRL on 2026-10-17). There is no GODEBUG opt-out. PeerDB dials TLS against user-supplied endpoints (Postgres/MySQL/Mongo sources; ClickHouse/Snowflake/Kafka/Elasticsearch destinations), so any peer presenting a chain through one of those intermediates will start failing handshakes once this image rolls out.

Not a reason to block — it is the intended security fix, and .github/workflows/*.yml already builds and tests on go-version 1.27.3, so this merely brings the container builder in line with CI. But it is probably worth a release-note line so support recognizes that failure mode instead of chasing it as a PeerDB regression.

No other regressions identified in the range for how this repo uses the toolchain (flow/go.mod declares go 1.27.0, so there is no language-version interaction).

Comment thread stacks/flow.Dockerfile
fi

FROM alpine:3.24@sha256:294b683cb724975bec92580e1e685676bd4b50bda910ddb8c51d4cabeaec77e6 AS flow-base
FROM alpine:3.24@sha256:be2656061b536c1883c4034790e21d0a09c5aaaf51968b89368a3c0371ea2c9a AS flow-base

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dep-bump review — alpine:3.24 294b683 → be26560 is 3.24.2 → 3.24.3. The new digest matches the 3.24.3 tag (pushed 2026-10-23); the old one was 3.24.2. The same digest is updated consistently at stacks/peerdb-server.Dockerfile:44, and no other alpine:3.24 pin exists in the repo, so the bump is complete.

Per the 3.21.9 / 3.22.7 / 3.23.7 / 3.24.3 announcement this is a pure patch release with no breaking changes inside the 3.24 series, carrying:

The packages these stages actually install (ca-certificates + geos here; ca-certificates, postgresql-client, curl, iputils in peerdb-server.Dockerfile) see no ABI or behavior breaks.

Cross-cutting note: the ca-certificates refresh is the same eMudhra distrust as the Go 1.27.3 crypto/x509 change flagged on line 3, and it affects the Go runtime system cert pool in this image. nexus is largely insulated, since postgres-connection and the reqwest / mysql_async clients use rustls with bundled webpki-roots rather than the system store.

The pinned AWS RDS bundle ADD --checksum= is untouched by this PR, as expected. Net: strictly a security patch.

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from 89f258b to 3db2500 Compare November 4, 2026 15:10
@claude

claude Bot commented Nov 4, 2026

Copy link
Copy Markdown

Renovate review: digest bumps reviewed, looks clean ✅

Diff is 3 lines across stacks/flow.Dockerfile and stacks/peerdb-server.Dockerfile, both image digest pins. No findings — no secret/PII output changes, and no files under a docs/tricky-areas.md path are touched.

What the digests actually resolve to (Renovate labels these "digest" updates, but both move real versions):

Pin Before After
golang:1.27-alpine 8a5910f = 1.27.1-alpine3.24 (pushed 2026-09-21) d200d2d = 1.27.3-alpine3.24 (pushed 2026-10-27)
alpine:3.24 (both files) 294b683 = 3.24.2 be26560 = 3.24.3 (2026-10-21)

Upstream notes for the bumped range

  • Go 1.27.2 (2026-10-08) — security fixes in go cmd, crypto/tls, html/template, net/http, net/textproto, os; plus compiler/linker/runtime fixes. Known upstream regression in this release is the export-data v5 format breaking older golangci-lint/staticcheck (golang/go#82106) — not relevant here, this image only builds the binary; lint runs on its own toolchain.
  • Go 1.27.3 (2026-10-19) — single security fix in crypto/x509 (CVE-2026-111943): verification now rejects any chain containing one of eight compromised eMudhra intermediate SPKIs. This is the only user-visible behaviour change in the bump: a mirror whose source/destination TLS certificate chains through those intermediates will start failing verification once this image ships. That is the intended fix, and it only takes effect on rebuild — so this PR is what actually delivers it for peer-flow.
  • Alpine 3.24.3 (2026-10-21) — ca-certificates (same eMudhra distrust, which also covers the Rust peerdb-server runtime), musl CVE-2026-107891, zlib CVE-2026-85091, and the 2026-09-29 OpenSSL advisory batch. Patch release within the 3.24 branch, no package major bumps.

Compatibility checks

  • flow/go.mod requires go 1.27.0, satisfied by 1.27.3; no toolchain directive to keep in sync.
  • flow.Dockerfile builds with CGO_ENABLED=1 against geos-dev/musl, so the builder's Alpine branch has to match the runtime's. 1.27-alpine still resolves to alpine3.24, same branch as the alpine:3.24 runtime — no musl/geos ABI skew.
  • Both alpine:3.24 pins were updated together; grep confirms no stale 294b683/8a5910f references remain anywhere in the repo.
  • docker-build (ubuntu-latest) passed on this head.

Sources: Go release history, Alpine 3.24.3 release post

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from 3db2500 to 5967ed6 Compare November 4, 2026 21:23
@claude

claude Bot commented Nov 4, 2026

Copy link
Copy Markdown

Reviewed this digest bump — no findings, looks clean to merge.

What the digests actually resolve to

Pin Old New Verified upstream
alpine:3.24 294b683 = 3.24.2 be26560 = 3.24.3 (2026-10-21) matches live 3.24/3.24.3 tag
golang:1.27-alpine 8a5910f (1.27.1, pinned in #4874 on 2026-09-30) d200d2d = 1.27.3-alpine3.24 matches live 1.27-alpine tag

So the bumped range is Alpine 3.24.2 → 3.24.3 and Go 1.27.1 → 1.27.2 → 1.27.3.

Release notes for the bumped range

Alpine 3.24.3 — part of the coordinated 3.21.9/3.22.7/3.23.7/3.24.3 security release. Contains OpenSSL CVE fixes (CVE-2026-35189, -42772, -54872/3/5, -72897, -75804/5/6, -77696, -84782/4) and PHP fixes (CVE-2026-109618/9). PHP is not installed in either image; the OpenSSL fixes do benefit curl/postgresql-client in the runtime stages. Patch-level only — no ABI or package-major changes affecting ca-certificates, geos, or iputils.

Go 1.27.2 — security fixes in cmd/go, crypto/tls, html/template, net/http, net/textproto, os (mostly HTTP/2 DoS/framing issues and two CONNECT connection-desync bugs), plus bug fixes in the compiler, linker, runtime, compress/flate, crypto/mlkem, encoding/json, encoding/json/v2. Notably this release fixes three encoding/json regressions filed against 1.27.0/1.27.1 (UnsupportedValueError.Value left invalid, ±Inf stored on float overflow, Decoder.InputOffset after EOF). Since PeerDB is now on the json/v2-backed encoding/json, that is a net improvement for this repo rather than a risk.

Go 1.27.3 — expedited release for CVE-2026-111943: crypto/x509 Verify now filters out chains containing eight specific eMudhra intermediates. This is the one genuine behaviour change in the range, and it is intended upstream hardening: the flow worker's outbound TLS to source/destination databases would now reject a chain running through those intermediates. Worth awareness only — CI already pins go-version: '1.27.3', so this is already the behaviour of the tested binaries; this PR just brings the Docker builder in line (it was lagging at 1.27.1).

Other checks

  • Both alpine:3.24 pins (stacks/flow.Dockerfile:33, stacks/peerdb-server.Dockerfile:44) were updated to the same digest — no split-brain base image.
  • No stale copies of the old digests anywhere else in the repo (compose files, Tiltfile, workflows).
  • Builder (golang:1.27-alpine → 1.27/alpine3.24) and runtime (alpine:3.24) move together, so the CGO-enabled binary's musl and geos/geos-dev versions stay matched.
  • No logging/stdout/stderr changes, so nothing touching the PII/secret-exposure rule.
  • No section in docs/tricky-areas.md covers stacks/, so no tricky-area checklist applies.

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from 5967ed6 to daacf7c Compare November 4, 2026 23:34
@renovate renovate Bot changed the title chore(deps): update dockerfile dependencies Update dockerfile dependencies Nov 4, 2026
@claude

claude Bot commented Nov 4, 2026

Copy link
Copy Markdown

Review: digest bump — looks clean ✅

Digest-only bump of two pinned base images in stacks/flow.Dockerfile and stacks/peerdb-server.Dockerfile. No tag changes, no Dockerfile logic changes.

Digest verification

Both new digests resolve to the current multi-arch manifests of the tags they are pinned against (checked via Docker Hub registry metadata) — no tag drift, no accidental cross-major move:

Image Old New Resolves to
golang:1.27-alpine 8a5910f (Go 1.27.1, alpine3.24) d200d2d Go 1.27.3, alpine3.24 — matches 1.27-alpine today
alpine:3.24 294b683 (3.24.2) be26560 3.24.3 — matches 3.24 today

Both alpine:3.24 pins in the repo (flow.Dockerfile:33, peerdb-server.Dockerfile:44) were bumped together, so no split-brain base image.

Upstream changes in the bumped range (regression check)

Go 1.27.1 → 1.27.3 — two patch releases, both security-driven, no language/behaviour changes:

  • Go 1.27.2 (2026-10-08): security fixes in the go command, crypto/tls, html/template, net/http, net/textproto, os; bug fixes in the compiler, linker, runtime, compress/flate, crypto/mlkem, encoding/json, encoding/json/v2, net/http, os.
  • Go 1.27.3 (2026-10-19): crypto/x509 fix (CVE-2026-111943, Go's first URGENT-track release) — rejects any chain through eight eMudhra intermediate CA keys that Mozilla added to OneCRL on 2026-10-17.

Alpine 3.24.2 → 3.24.3 (release post, 2026-10-21): OpenSSL CVE fixes (CVE-2026-35189, -42772, -54872/3/5, -72897, -75804/5/6, -77696, -84782, -84784) plus PHP fixes (not used here).

No regressions identified in either range — these are pure patch releases. One behavioural note worth being aware of rather than a blocker: after Go 1.27.3, peer-flow will refuse TLS connections to any peer whose server certificate chains through one of the eight blocked eMudhra intermediates. That's the intended upstream security behaviour (browsers distrust the same keys), and such certs are very unlikely on database/warehouse endpoints, but it is the one way this bump can change runtime behaviour.

Bonus

The Go bump actually removes drift: CI already builds and lints with Go 1.27.3 (.github/workflows/flow.yml, ci.yml, golang-lint.yml, cleanup.yml, tilt-flow.yml), while the release image was still compiling on 1.27.1. This brings the shipped binary in line with CI.

No paths in this diff fall under a docs/tricky-areas.md section. No secret/PII output introduced. docker-build is green.

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from daacf7c to e4e096f Compare November 4, 2026 23:39
@claude

claude Bot commented Nov 4, 2026

Copy link
Copy Markdown

Reviewed this Renovate digest bump — looks clean, no findings.

What changed

Image Before After Resolves to
alpine:3.24 (stacks/flow.Dockerfile:33, stacks/peerdb-server.Dockerfile:44) 294b683 be26560 Alpine 3.24.2 → 3.24.3 (released 2026-10-21)
golang:1.27-alpine (stacks/flow.Dockerfile:3) 8a5910f d200d2d Go 1.27.2 → 1.27.3, 1.27.3-alpine3.24 (pushed 2026-10-27)

Regression check (upstream notes)

  • Go 1.27.3 is a security-only release: crypto/x509 gains a deny list for eight compromised eMudhra intermediate CA keys (CVE-2026-111943, handled on the Go security URGENT track). No compiler/runtime/stdlib behaviour changes beyond that, so no regression risk for the flow worker. Worth being aware of the one behavioural consequence: any TLS chain presented by a source/destination that happens to chain through one of those eight intermediates will now be rejected at verification. That is the intended fix, not a bug, but it is the only user-visible change in the bump.
  • Alpine 3.24.3 is a patch release within the same 3.24 branch (supported until 2028-06-01): ca-certificates drops the compromised eMudhra intermediates, plus CVE fixes in musl (CVE-2026-107891), zlib (CVE-2026-85091), openssl, and php. No ABI or package-set changes — ca-certificates, geos, postgresql-client, curl, iputils all still resolve on 3.24.

Consistency checks

  • Both alpine:3.24 pins moved together; grep finds no remaining reference to the old 294b683 digest anywhere in the repo.
  • The builder stays on the alpine3.24 variant (golang:1.27-alpine → 1.27.3-alpine3.24), so builder and runtime still share the same musl/Alpine base.
  • Go 1.27.3 matches the go-version: 1.27.3 already pinned across .github/workflows/{ci,flow,golang-lint,cleanup,tilt-flow}.yml, so this bump removes drift between the CI toolchain and the shipped image rather than introducing it. go.mod requires go 1.27.0, satisfied.
  • No new stdout/stderr/log output, and nothing under a docs/tricky-areas.md path is touched.
  • docker-build (ubuntu-latest) is green on this PR.

LGTM — this is a security patch bump in the desirable direction.

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from e4e096f to 559704e Compare November 5, 2026 03:37
@claude

claude Bot commented Nov 5, 2026

Copy link
Copy Markdown

Reviewed this Renovate digest/patch bump — looks clean, no findings.

Digest verification — all three pins resolve to the exact tags claimed (current Docker Hub manifest-list digests):

Image Pinned Matches tag
alpine:3.24 be265606… ✅
golang:1.27-alpine d200d2dd… ✅
node:24.22.2-alpine 8a32c8cf… ✅

Regression check on the bumped range

  • alpine 3.24 digest (294b683 → be26560) — 3.24.2 → 3.24.3 point release. Package deltas: libcrypto3/libssl3 3.5.8-r0 → 3.5.9-r0, musl/musl-utils 1.2.6-r2 → -r3, zlib 1.3.2-r0 → -r1, ca-certificates-bundle 20260909-r0 → 20261020-r0. All patch-level/security refreshes, no soname or major-version moves. The only thing worth a passing thought is the CA bundle refresh (root store churn can in principle drop a distrusted root), but nothing in this repo pins a specific root — flow.Dockerfile adds the AWS RDS global bundle separately via a checksummed ADD, which is untouched.
  • golang 1.27-alpine digest (8a5910f → d200d2d) — still Go 1.27.3 on Alpine 3.24.3; this is a base-image refresh picking up the same openssl/musl/zlib patches, not a Go version change. Worth noting because flow.Dockerfile builds with CGO_ENABLED=1 against geos-dev in the builder and links against geos from alpine:3.24 at runtime — builder and runtime stay on the same Alpine major here, so the geos soname stays aligned.
  • node 24.22.1 → 24.22.2 — LTS patch, release notes are five V8 backports plus stream: keep async context of parked writes (#66907). The headline fix is a crash when Error.stackTraceLimit is set very high/Infinity, a regression from the earlier stack-trace perf optimization — so this release removes a regression rather than introducing one. The October security fixes (CVE-2026-111497 brotli RCE, CVE-2026-105482, CVE-2026-106069, CVE-2026-105481, CVE-2026-105483) all landed in 24.22.1, which main already had. Image base is Alpine 3.24.3, consistent with the runtime stages.

Consistency — both alpine:3.24 pins in the repo (stacks/flow.Dockerfile:33 and stacks/peerdb-server.Dockerfile:44) were updated to the same digest; grep shows no other alpine/node/golang pin left behind. No other file references a Node version to keep in sync.

Review checklist — no stdout/stderr/log changes, so the PII/secrets rule is N/A. No changed path falls under a docs/tricky-areas.md section (the file only covers mirror config vs workflow state and per-mirror behaviour).

docker-build (ubuntu-latest) is green on these digests.

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: TestApiMy/TestResyncWithSnapshotConfigOnRunningPipe hit a 3-minute "wait for flow dropped" timeout in only the mysql-gtid_ch-lts cell, while the identical package/MySQL image passed in mysql-gtid_ch-latest and sibling tests using the same terminate-and-drop path passed in the same job, on a Renovate Dockerfile PR unrelated to flow termination.
Confidence: 0.85

✅ Automatically retrying the workflow

View workflow run

@renovate
renovate Bot force-pushed the renovate/dockerfile branch from 559704e to 92f4e8e Compare November 5, 2026 17:41
Comment thread stacks/flow.Dockerfile
# syntax=docker/dockerfile:1.28@sha256:bb22d9815c728170f72750f4e5b0d672e06176142e1d602c7e66c050100b7e5b

FROM golang:1.27-alpine@sha256:8a5910f31396cd4d89662f56c68b3ae31d374308270a1c3bd96672ee5ed43414 AS builder
FROM golang:1.27-alpine@sha256:d200d2dd76b03a99b52651fd1325aff7dcd35422c35c01bac56571b0507f3deb AS builder

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This digest bump is not a pure base-image refresh — it moves the Go toolchain used to build the shipped flow binaries from 1.27.1 → 1.27.3. (An earlier review comment on this PR stated the Go version was unchanged; that is incorrect.)

Docker Hub tag→digest mapping:

Digest Resolves to
8a5910f3… (old) golang:1.27.1-alpine3.24, built 2026-09-21
d200d2dd… (new) golang:1.27.3-alpine3.24 = 1.27-alpine, built 2026-10-27

So the bumped range spans two security releases:

  • Go 1.27.2 (2026-10-08) — security fixes to the go command and crypto/tls, html/template, net/http, net/textproto, os.
  • Go 1.27.3 (2026-10-19) — security fix to crypto/x509 (CVE-2026-111943): the verifier now rejects any chain passing through eight eMudhra intermediate CA keys (added to Mozilla OneCRL on 2026-10-17).

No change requested — the bump is desirable, and it also aligns the image builder with CI, which already pins go-version: 1.27.3 across the flow / ci / golang-lint / cleanup / tilt-flow workflows; released images were previously built with an older toolchain than CI tested against.

Worth flagging to reviewers, though: the crypto/x509 change is a user-visible TLS behaviour change in the shipped binaries, not just a build-time detail. Any mirror whose source or destination certificate chains through one of those intermediates will start failing verification once this image ships. Intended security hardening, but it may belong in release notes.

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: Not a test failure at all — the cockroachdb-v24_ch-lts job died during environment setup when curl fetching the PGDG apt signing key from www.postgresql.org returned "curl: (56) Failure when receiving data from the peer" after 25s of zero bytes, a transient network flake (all 23 sibling jobs passed the same step, and the PR is an unrelated Renovate Dockerfile bump).
Confidence: 0.97

✅ Automatically retrying the workflow

View workflow run

@renovate
renovate Bot merged commit 7102079 into main Nov 6, 2026
71 of 74 checks passed
@renovate
renovate Bot deleted the renovate/dockerfile branch November 6, 2026 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant