Skip to content
Cade's Dotfiles

Upgrade finishes installing, then the version audit calls newer tools outdated

Page source

Source: Troubleshooting reference

Symptom: bootstrap.sh upgrade installs current Homebrew packages, passes runtime verification, then fails its strict version audit because an installed patch version is newer than the reported exact baseline.

Root cause: an unpinned package-manager tool was audited as an exact pin. A Homebrew upgrade could therefore make the machine newer than the repo baseline, and the audit categorized every exact mismatch as outdated.

Confirm:

Terminal window
bash install/audit-versions.sh | jq '.[] | select(.status != "current")'
brew info --json=v2 rustup juliaup | jq '.formulae[] | {name, stable: .versions.stable, installed: .installed[0].version}'

Fix: update the repo, then rerun bootstrap.sh upgrade. Unpinned rustup, juliaup, and unversioned Homebrew zig releases use minimum-version floors; genuinely pinned toolchains remain exact.

Quarto follows the same ownership rule: the macOS Homebrew cask uses a minimum floor of 1.10.18, so an installed 1.10.19 passes. Linux uses an exact release archive pin, including an explicit DF_QUARTO_VERSION override. An older audit applied the Linux pin on macOS and incorrectly rejected newer cask releases. After updating the audit, rerun bash install/audit-versions.sh --strict; a successful report requires every row to have status: current and exits zero.