Fleet status
Every repo carries two version lines — its own release tag and the Core it vendors. This board reads both from GitHub when the site is built and flags any repo behind the latest Core release.
| Repo | Layer | Release | Vendored Core | Status |
|---|---|---|---|---|
| dotfiles-core | Core | v3.2.0 | reference | — |
| dotfiles-Alpine | OS-native | v1.3.11 | 3.2.0 | current |
| dotfiles-Arch | OS-native | v1.3.11 | 3.2.0 | current |
| dotfiles-Fedora | OS-native | v1.3.11 | 3.2.0 | current |
| dotfiles-Gentoo | OS-native | v1.3.11 | 3.2.0 | current |
| dotfiles-MacBook | OS-native | v1.3.11 | 3.2.0 | current |
| dotfiles-openSUSE | OS-native | v1.3.11 | 3.2.0 | current |
| dotfiles-Defense | Role | v1.0.11 | 3.2.0 | current |
| dotfiles-Kali | Role | v1.3.11 | 3.2.0 | current |
| dotfiles-Windows | Native host | v1.1.6 | replicated | — |
Drift, integrity, and pin freshness are enforced in CI (fleet-drift, core-integrity, freshness); this page is the read-only glance. See the architecture for how Core vendoring works.