Repository navigation
Doc-consistency tests fail after auto-release across tool repos #5
Description
Activity
- added 17 commits that reference this issue
on Apr 25, 2026 Resolved by Phase 2 work:
- PR feat: add release-doc-sync composite action (Phase 2a, refs #5) #19 (v1.8.0): release-doc-sync composite action created
- PR fix: release-doc-sync action checkout pollutes caller's working tree #20+fix: defensive cleanup of release-doc-sync workspace checkout (v1.8.2) #21 (v1.8.1+v1.8.2): action checkout pollution fixed
- Docker integration PR fix: release.yml tag introspection and floating tag automation #26: smoke tested
- Steam chore: finish Phase 1 with standards template and scaffold updates #6, Home-Lab fix: composite action propagates checker exit code to caller #15, Monday Reconcile validate-counts vs drift checker stale-counts pattern across ecosystem #12, CFX feat: drift checker CI integration (Phase 2 Session C) #9, Unity feat: drift checker core library (Phase 2 Session A) #7: parallel rollout
- Test relaxations: Docker fix: version-bump-check parser silently passes all PRs #28 and Steam feat: drift checker core library (Phase 2 Session A) #7
- Backfill of stale references: Phase 2e (next session)
The action now keeps CHANGELOG, CLAUDE.md (where applicable), and ROADMAP Current: in sync with plugin.json on every auto-release across all 6 auto-releasing tool repos. Tests that asserted behavior we explicitly do not want (roadmap table rows for patch releases) have been removed.
During Phase 1 rollout (Issue #1), Docker-Developer-Tools and Steam-Cursor-Plugin had failing doc-consistency tests:
All check that CHANGELOG.md, ROADMAP.md, and CLAUDE.md reference the current plugin.json version. The failures occur because release.yml bumps plugin.json but does not update those docs. Every auto-release creates stale docs that the test suite then flags.
Observed on: Docker-Developer-Tools, Steam-Cursor-Plugin.
Pattern likely exists in any tool repo with both auto-release AND doc-consistency tests.
Fix options:
The auto-release pattern is ecosystem-wide (6 of 8 active repos auto-released during Phase 1), so this drift is recurring rather than a one-time bug.