Repository navigation
Upgrade notes
Staleness now uses git history. In a git repository, maat check flags a doc when a commit after its last update touched one of its related_code paths, instead of comparing file timestamps. This works reliably in CI for the first time, and timestamp-only changes (formatters, branch switches, rebases) no longer cause false positives.
Action needed: set fetch-depth: 0 on actions/checkout in your workflow. With a shallow clone, check can't see older commits and warns about it.
You may see new warnings. Drift that timestamps never revealed now shows up. It stays a warning unless you use --strict.
To keep the old behavior, set check.staleness_source: mtime in .maat.yml. See ADR 0012.
Changelog
- 10ad766: Update README.md (@UemitCebi)
- e4303d8: feat(check): detect staleness from git history (@UemitCebi)
Contributors
UemitCebi