Skip to content

docs: correct the SQLite migration count (182 -> 183) breaking every PR's docs gate - #14717

Closed
gonisulaimann wants to merge 1 commit into
diegosouzapw:release/v3.8.51from
gonisulaimann:fix/release-v3.8.51-migration-count-docs
Closed

gonisulaimann wants to merge 1 commit into
diegosouzapw:release/v3.8.51from
gonisulaimann:fix/release-v3.8.51-migration-count-docs

Conversation

@gonisulaimann

Copy link
Copy Markdown
Contributor

The strict docs-accuracy gate ("Docs accuracy — fabricated-docs + i18n mirrors, strict") is failing on every PR with three drift errors since the merge wave landed migration #183:

✗ README.md — stale migrations: "182 migrations" — code has 183
✗ AGENTS.md — stale migrations: "182 migrations" — code has 183
✗ llm.txt — stale migrations: "182 migrations", "182 versioned SQL migration", "182 SQL migrations" — code has 183

Example run: https://github.com/diegosouzapw/OmniRoute/actions/runs/35945840872 (tracked under the base-red issue #14547, alongside the env-doc drift that #14683 fixes).

What changed

  • README.md, AGENTS.md, llm.txt: 182 → 183 migrations (5 phrasings in llm.txt).
  • Re-propagated the 66 docs/i18n/<locale>/llm.txt strict mirrors via scripts/i18n/sync-llm-mirrors.mjs.
  • Changelog fragment per convention.

Verification

⚠️ base-red inherited: #14547 (typecheck/unit failures unrelated to this docs fix).

The merge wave landed migration diegosouzapw#183 without updating the documented
count, so the strict docs-accuracy gate now fails on every PR CI run
with three drift errors (README.md, AGENTS.md, llm.txt). Update the
root docs and re-propagate the llm.txt mirrors via
scripts/i18n/sync-llm-mirrors.mjs (66 locales).
@diegosouzapw

Copy link
Copy Markdown
Owner

Thanks @gonisulaimann — exactly the right diagnosis. The same 182 → 183 migration-count sync (README, AGENTS.md, llm.txt and the 66 mirrors) landed a few minutes earlier as #14714, so the docs gate is already green on the tip. Closing as a duplicate. (merge-batch 2026-09-24)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants