docs(v1.10.0): name sqlite3/bc/dc/column in the Hub description tool list
DOCKER_HUB.md is POSTed to Docker Hub as full_description by the update-description job, and CI reads it from the TAG, not from main. Its "Modern CLI tooling" list said "Data: jq, yq" while this release adds sqlite3, bc, dc and column to the base - so the public page would have shipped incomplete for the whole v1.10.0 cycle and the fix could not land until the next tag. Caught by the pre-tag doc sweep rather than by a gate: check-doc-drift.sh verifies version CLAIMS (pins, Node major) against the build files, but it cannot know that a hand-written feature list grew stale, because nothing declares that list's contents. Same failure shape as the v1.9.0 Node 22/24 mismatch that shipped eight releases running. README carries no equivalent list, so there is nothing to mirror.
This commit is contained in:
+1
-1
@@ -80,7 +80,7 @@ The entrypoint deploys/registers all of these on first container start. Re-runni
|
||||
- **Editor**: neovim (system-wide `termguicolors` default; bring your own config/plugins), tmux (configured for 0-indexed sessions)
|
||||
- **Search/nav**: ripgrep, fd, fzf, zoxide
|
||||
- **Display**: bat, eza, htop, tree
|
||||
- **Data**: jq, yq
|
||||
- **Data**: jq, yq, sqlite3, bc/dc, column
|
||||
- **Help**: tldr (tealdeer — Rust port; run `tldr --update` once to populate cache)
|
||||
- **Git**: git-lfs, git-crypt, gitleaks (for pre-commit secret scanning)
|
||||
- **Build**: gcc, g++, make, patch
|
||||
|
||||
Reference in New Issue
Block a user