Repository navigation
chore(tools): bump Docker toolchain to latest stable versions - #763
arcbox-labs[bot] wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Auto-generated toolchain-bump PR (cargo xtask release check-tool-updates); reviewed the lockfile diff and independently re-verified the pin against the same sources the generator uses.
kubectl1.37.1 → 1.37.2 — the kubernetes-group entry inassets.lockonly: version plus the two darwin SHA-256 pins. Nothing else in the file moved and the[boot]bundle pins are untouched.
Verification:
https://dl.k8s.io/release/stable.txtreportsv1.37.2, so the pin is current.- Downloaded both darwin artifacts from the pinned URL templates (
dl.k8s.io/release/v1.37.2/bin/darwin/{arm64,amd64}/kubectl) and recomputed SHA-256: both match the recorded values (55701af0…arm64,88379aff…x86_64). - No stale
1.37.1pins elsewhere in the repo; the two grep hits are an unrelatedArcBox Devapp version indocs/logs/2026-10-09-https-validation-preparation.md.
Two boilerplate notes, neither an issue with this change: the body's "check against the guest dockerd" warning only ever applies to the docker tool (assets.lock header) — kubectl is kubernetes-group with no guest-side twin, so no boot-bundle coupling applies here; and the "Docker toolchain" title is hardcoded generator copy (.github/workflows/check-tool-updates.yml lines 66 and 85), which is why a kubectl-only bump carries it.
glm-5.3-flash | 𝕏
cdf868b to
fcfc583
Compare
There was a problem hiding this comment.
Important
The docker hunk diverges from the guest dockerd pinned in the boot bundle — hold it (or land it combined with a [boot] bump). The buildx, compose, and kubectl hunks verified clean.
Reviewed changes
Incremental review of the new commits since the prior pullfrog review (which covered the kubectl bump only): the branch now also bumps the three docker-group tools in assets.lock.
- Bumped
docker29.9.2 → 29.9.3,docker-buildx0.38.1 → 0.38.2 anddocker-compose5.6.1 → 5.7.0, each with fresh darwin sha256 pins. All six checksums match re-downloaded artifacts from the same URL templates the runtime uses, and all three versions are still the upstream latest (moby/moby,docker/buildx,docker/composelatest-release redirects). - Re-checked the guest-dockerd coupling the PR body warns about: the pinned boot bundle
v0.8.12(manifest hash matches the[boot]pin, and it is the newest boot-assets release) shipsdockerd29.9.2 — that makes thedockerhunk the one finding, inline below. kubectl1.37.2 unchanged since the prior review; old-version sweep outsideassets.lockis clean (only the guest-package text indocs/boot-assets.md, which legitimately tracks[boot]).
glm-5.3-flash | 𝕏
| version = "29.9.2" | ||
| arch.arm64.sha256 = "ea8a2ce5ac31f9f5f3fb711a7a485e1e46cc7a69798a629a70306f6e6af25b7a" | ||
| arch.x86_64.sha256 = "089c3f618df88bdef4f1257d9d604499136a1ec5168b67d194c260acad2b522f" | ||
| version = "29.9.3" |
There was a problem hiding this comment.
This bump diverges the host docker CLI (29.9.3) from the guest dockerd in the pinned boot bundle, which is still 29.9.2, with no [boot] bump in this PR to bound the gap. Per the assets.lock header the two pins should only diverge for the short window between a bundle release and the [boot] bump, and a generated PR whose docker hunk would diverge gets that hunk stripped, landing later as a combined [[tools]] + [boot] commit. No runtime breakage (the CLI tolerates an older daemon via API negotiation) — this is the release invariant, not a functional bug.
Technical details
# Hold the `docker` hunk until the boot bundle catches up (or land it combined with `[boot]`)
## Affected sites
- assets.lock:38-40 — `docker` `[[tools]]` bumped to 29.9.3 while the pinned boot bundle's guest dockerd stays 29.9.2.
## Evidence
- `[boot]` pins bundle `v0.8.12`; `https://boot.arcboxcdn.com/asset/v0.8.12/manifest.json` hashes to the recorded `manifest_sha256` (`4e1638ce…`), so the pin is live.
- That manifest's `binaries[]` report `dockerd`/`containerd`/`runc` = `29.9.2`.
- `https://api.github.com/repos/arcboxlabs/boot-assets/releases` lists `v0.8.12` (2026-10-31) as the newest bundle — no release shipping dockerd 29.9.3 exists yet.
- Host side is otherwise clean: all six new sha256 pins match re-downloaded artifacts from the `registry.rs::download_url` templates, and `moby/moby` / `docker/buildx` / `docker/compose` latest-release redirects confirm 29.9.3 / 0.38.2 / 5.7.0 are still current. `docker-buildx`, `docker-compose`, and `kubectl` have no guest twin and can merge freely.
## Required outcome
- The `docker` hunk must not merge ahead of a guest dockerd 29.9.3: either strip it from this PR (the other three hunks merge now), or hold the whole PR until a boot-assets bundle ships dockerd 29.9.3 and land `[boot] version` + `manifest_sha256` in the same PR as the `[[tools]]` bump.
## Notes
- The upstream `upstream.toml` for the bundle tag lives in the boot-assets repo; this PR's body links the procedure.fcfc583 to
3a3e969
Compare
There was a problem hiding this comment.
Important
The delta since the last review verifies clean, but the previously flagged hold still applies: the force-push re-applied the docker 29.9.3 hunk while the pinned boot bundle still ships guest dockerd 29.9.2 (v0.8.12 remains the newest boot-assets release, re-confirmed today). Strip the docker hunk from this PR — the other four hunks merge now — or hold until a bundle ships dockerd 29.9.3 and land [boot] + [[tools]] together. The open review thread tracks this.
Reviewed changes
Incremental review of the delta since the prior pullfrog review (fcfc583 → 3a3e969d, generator force-push): two pins moved forward and a new tool hunk joined the PR.
- Re-bumped
docker-buildxanddocker-compose— now 0.38.1 → 0.39.0 and 5.6.1 → 5.7.1, superseding the 0.38.2 / 5.7.0 pins of the previous head. - Added a
docker-credential-osxkeychainhunk — 0.9.12 → 0.9.13, not present in the previous head. dockerandkubectlhunks unchanged from the prior head (29.9.3 and 1.37.2 respectively).
Verification (downloads and latest checks use the same URL templates and endpoints the generator and runtime use):
- All six new sha256 pins for buildx 0.39.0, compose 5.7.1 and osxkeychain 0.9.13 match re-downloaded artifacts (Binary-format checksums).
/releases/lateststill reportsv0.39.0/v5.7.1/v0.9.13/docker-v29.9.3— every bumped version is upstream current.- Old-version sweep outside
assets.lockis clean; the0.9.12hits are the unrelatedparking_lot_corecrate (Cargo.lock,NOTICE.md). - Guest-dockerd coupling re-checked today:
latest.jsonsays0.8.12, the boot-assets releases API still listsv0.8.12(2026-10-31) as newest, and its manifest reportsdockerd/containerd/runc=29.9.2— thedockerhunk still diverges; tracked in the open review thread, not re-raised inline.
glm-5.3-flash | 𝕏

Summary
docker: 29.9.2 -> 29.9.3docker-buildx: 0.38.1 -> 0.39.0docker-compose: 5.6.1 -> 5.7.1docker-credential-osxkeychain: 0.9.12 -> 0.9.13kubectl: 1.37.1 -> 1.37.2Checksums verified by downloading binaries and computing SHA-256.
Before merging a
dockerbump: check it against the guest dockerd in the boot bundle[boot]pins (upstream.tomlat that tag in the boot-assets repo). See the header ofassets.lock— the two are meant to diverge only between a bundle release and the[boot]bump. buildx and compose have no guest-side twin.