Repository navigation
chore: update cloudflared to 2026.10.3 and refresh Debian base - #31
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Uses the latest stable cloudflared release, including Go security updates and the fix for messages truncated beyond the read buffer. The Dockerfile retains the shell required by the login helper. Updates release notes in all five locales and documents how to refresh the base image digest.
Evidence
origin/mainpackages cloudflared2026.10.0:0, SDK3.0.6, and an unpinned Debian base.After:
make x86passes TypeScript, SDK lint, formatting, bundling, image build, and S9PK packing. The packed manifest reports2026.10.3:0, SDK3.1.0, and minimum StartOS0.4.0.2.13-slimdigest is also the current13.7-slimdigest.cloudflared --version, required daemon/action flags, ingress validation and hostname matching, shell and CA bundle, and login-helper syntax and required-session validation. The packaged binary's SHA-256 matches the tested container; the packaged root filesystem reports Debian13.7.3816299e0a54f0be9b5544e562c448fbdd0b503a.simple-strip.local(StartOS0.4.0.2, x86_64) passed: installed2026.10.3:0/ SDK3.1.0from exact commit3816299e0a54f0be9b5544e562c448fbdd0b503a. The service resumed running with a successful primary health check, no service error, and no outstanding tasks. Container checks report cloudflared2026.10.3and Debian13.7; the tunnel configuration file's SHA-256 is unchanged across the upgrade.https://registry.testnet4.info/returned HTTP200in approximately0.11s, with valid TLS,server: cloudflare,cf-cache-status: DYNAMIC, and the expected Start9 Marketplace HTML (13,248bytes).start-cli 2.4.2for server management because CLI2.5.0request signatures require StartOS0.4.0.3or later. The system CLI installation was unchanged.Merge Danger
Door: two-way
No data migration is added. Reverting restores the previous package source pins.
Blast Radius: service
Changes the cloudflared binary, Debian runtime, and SDK used by Cloudflare Tunnel.