You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(image): upgrade every runtime image package at build time (OpenSSL 3.5.9-r1, advisory 20261110) #910
The runtime image installs libssl3 and libcrypto3 3.5.9-r0. Alpine v3.24 shipped 3.5.9-r1 on Nov 18 (aports 0f4c7e8d, OpenSSL advisory 20261110; OSV ALPINE-CVE-2026-88822, -88823, -95691, -95692, -107496, all rated Low). git-remote-https links libssl/libcrypto through libcurl and ssh-keygen links libcrypto. The pinned base alpine:3.24.4 still carries 3.5.9-r0, and no 3.24.5 exists.
Desk decision
P0. Replace the zlib-only line with a plain apk upgrade --no-cache in the runtime stage, so each future base fix needs no new line (this also keeps zlib at 1.4-r0). Update the Dockerfile comment and docs/how-to/deploy-production.md. Prove with apk list -I on amd64 and arm64 that libssl3, libcrypto3 and zlib are current and that the rest of the package set is unchanged apart from upgrades. Lanes: image.yml publish=false dispatch, the ci.yml image job, the Compose quickstart smoke, the docs gate. Must land before release PR #812 merges.
Dependency audit 2026-11-20.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: medium
Landed in #913 as d6fbebe (merge queue, 2026-11-20 12:25Z). Post-merge ci run 44735617690 and release-please run 44735617943 passed, and release PR #812 now lists the fix for 0.21.0.
The runtime stage runs a plain apk upgrade --no-cache. The image now holds libssl3 and libcrypto3 3.5.9-r1 and zlib 1.4-r0 on amd64 and arm64.
The apk list -I outputs of main's Dockerfile and the PR head differ only in libcrypto3 and libssl3 (3.5.9-r0 to 3.5.9-r1). Both builds hold the same 60 packages. apk upgrade made 3 upgrades and nothing else.
The image.yml publish=false lane cannot build a branch, because it builds the release tag it is given (image.yml lines 74 and 115). The CI image job builds the PR head natively on both platforms, so it served as the native lane. It now prints apk list -I on every run.
The first image.yml run that builds this Dockerfile is the publication run of the next release. Its stage log will show the three Upgrading lines.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: xhigh
Activity
fix(image): upgrade every runtime image package at build time
docs(deploy): say plainly what the runtime apk upgrade does
ThomasK33 commentedon Nov 20, 2026
Landed in #913 as d6fbebe (merge queue, 2026-11-20 12:25Z). Post-merge
cirun 44735617690 andrelease-pleaserun 44735617943 passed, and release PR #812 now lists the fix for 0.21.0.apk upgrade --no-cache. The image now holds libssl3 and libcrypto3 3.5.9-r1 and zlib 1.4-r0 on amd64 and arm64.apk list -Ioutputs of main's Dockerfile and the PR head differ only in libcrypto3 and libssl3 (3.5.9-r0 to 3.5.9-r1). Both builds hold the same 60 packages.apk upgrademade 3 upgrades and nothing else.apk list -Ion every run.Upgradinglines.Generated with
xum• Model:anthropic:claude-opus-5-5• Thinking:xhigh