Skip to content

v2.4.0 — migrate-incident path fix + fix-legacy-layout

Latest

Choose a tag to compare

@TheGlitchKing TheGlitchKing released this 15 May 02:18
· 8 commits to main since this release
24fbd0a

Bug fix + recovery command for the 2.3.0 migrate-incident target-path issue.

In 2.3.0, hewtd migrate-incident wrote folders OUTSIDE <vault-root>/incidents/, which the incidents/INDEX.md generator silently missed. Discovered in real-world use — 4 legacy postmortems in investorhub required manual mv to populate the index.

What's fixed

  • migrate-incident now writes to the canonical <vault-root>/incidents/<slug>/ (no manual mv required).
  • Idempotency check covers both the canonical and 2.3.0-legacy locations; surfaces the legacy case explicitly.
  • New --force flag overrides the idempotency guard.

What's new

  • hewtd fix-legacy-layout — relocates 2.3.0-buggy folders into <vault>/incidents/, rewrites provenance: refs in fact files (handles both qualified and bare-slug refs). Idempotent. --dry-run supported.

Migration for consumers stuck on 2.3.0 layout

npx --no @theglitchking/hit-em-with-the-docs fix-legacy-layout --dry-run
npx --no @theglitchking/hit-em-with-the-docs fix-legacy-layout
npx --no @theglitchking/hit-em-with-the-docs maintain

No breaking changes to the public API (src/index.ts exports unchanged).

See CHANGELOG.md for the full entry.

Stats: 241/241 tests passing (was 230 at 2.3.0; +11 new). PR #6.