Tags give the ability to mark specific points in history as being important
-
checkdocs-v2026.12
f4e9e515 · ·checkdocs v2026.12: .gitattributes is a managed region so projects can keep LFS rules (#54), sbom job fixed (#55)
-
checkdocs-v2026.11
495778c5 · ·checkdocs v2026.11: print the manifest notice as a closing NOTICE block (#56)
-
checkdocs-v2026.10
41145e7e · ·checkdocs v2026.10: dest_is_safe rejects rooted/prefixed paths on every platform (#42); anyhow 1.0.104 (#43)
-
checkdocs-v2026.9
5d0df23d · ·checkdocs engine v2026.9 Adds the per-entry missing_markers_severity manifest field (#32): a part-project managed file (e.g. the CLAUDE.md preamble) whose claude-quickstart:managed markers are absent now surfaces as a non-blocking exit-3 advisory nudge instead of a blocking violation, so a first migration's CI isn't reddened by the one-time manual marker step. Additive + backward-compatible (engines before v2026.9 ignore the field and keep blocking).
-
checkdocs-v2026.8
2393dade · ·checkdocs engine v2026.8 Re-cut after #29 moved the audit-claude-md gate into the checkdocs crate, bumped ENGINE_VERSION to (2026,8), and restored the is_template_repo crate-root re-export that v2026.7 omitted (B-1: a Case-A downstream pinning v2026.7 + main's validate.rs failed to compile). #30 adds the engine-version-guard so a checkdocs crate change can never again ship under a stale tag.
-
checkdocs-v2026.7
800c78fa · ·checkdocs engine crate v2026.7 The check-docs sync engine, extracted as a versioned workspace library crate (ADR-002). Downstreams consume it by pinning this tag in xtask/Cargo.toml: checkdocs = { git = "https://gitlab.com/gadhs/templates/claude-quickstart.git", tag = "checkdocs-v2026.7" } ENGINE_VERSION (2026,7); manifest min_engine_version v2026.4 (grammar unchanged).