Skip to content

docs: add historical documentation migration tooling - #259

Merged
nicklambourne merged 84 commits into
masterfrom
codex/legacy-docs-tooling
Aug 14, 2026
Merged

docs: add historical documentation migration tooling#259
nicklambourne merged 84 commits into
masterfrom
codex/legacy-docs-tooling

Conversation

@nicklambourne

Copy link
Copy Markdown
Owner

Historical documentation train 1/6.

Depends on #258 and records its final base commit as a188c2c.

This PR adds the migration contract and reproducible tooling:

  • freezes the authoritative origin/gh-pages inventory at 747ca39861503fbece849e375c9843641f87684c;
  • records all 22 published versions and 294 published routes;
  • adds deterministic conversion and fixture checks;
  • adds route, asset, symbol, and provenance inventories used by later PRs.

The source plan itself is intentionally not included.

Nicholas Lambourne and others added 8 commits August 14, 2026 14:11
Run push-triggered workflows only for master (PR branches already get
pull_request runs, and stacked branches previously got neither), and drop
the pull_request branches filter so pull requests targeting stacked train
branches receive checks before they are retargeted to master.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Nicholas Lambourne and others added 25 commits August 14, 2026 15:31
The docs-example test resolves the package by name at runtime, and the
docs build sets its own UV_CACHE_DIR so the setup-uv cache post-step
fails on an empty cache path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@nicklambourne
nicklambourne marked this pull request as ready for review August 14, 2026 12:59
@nicklambourne
nicklambourne changed the base branch from codex/release-2-1 to master August 14, 2026 12:59
@nicklambourne
nicklambourne merged commit ab00827 into master Aug 14, 2026
3 checks passed
@nicklambourne
nicklambourne deleted the codex/legacy-docs-tooling branch August 14, 2026 13:35
nicklambourne added a commit that referenced this pull request Aug 17, 2026
* chore: move Python package into workspace

* test: establish shared conformance contract

* feat: add TypeScript package

* ci: add coordinated package release automation

* docs: migrate site to Docusaurus

* feat: make docs language selection site-wide

* docs: complete language-specific guides

* feat: expose versioned documentation

* feat: standardise TypeScript block factory names

* docs: improve API reference generation and navigation

* test: enforce comprehensive conformance coverage

* feat: support current Block Kit blocks in Python

* feat: support current Block Kit blocks in TypeScript

* docs: bring TypeScript API reference to parity

* docs: add validated Block Kit previews

* ci: align monorepo validation

* chore: prepare 2.1.0 release

* docs: add legacy migration contract and tooling

* ci: give stacked pull requests check runs

Run push-triggered workflows only for master (PR branches already get
pull_request runs, and stacked branches previously got neither), and drop
the pull_request branches filter so pull requests targeting stacked train
branches receive checks before they are retargeted to master.


* ci: give stacked pull requests check runs


* ci: give stacked pull requests check runs


* ci: build the smoke package before switching to the matrix Node

pnpm 11.16 requires Node 22.13+, so the Node 20.19 smoke leg must install
and build under the runner's default Node and only then switch versions
for the import checks.


* ci: pin setup-uv to an existing tag

astral-sh/setup-uv publishes no moving v10 tag, so the docs workflow
could not resolve its action.


* ci: alias the package name for docs-example typechecking

The docs-example test imports docs/examples/typescript/section_hello.ts,
which imports the package by name; tsc needs the same alias vitest uses.


* ci: resolve the package alias in vitest and skip the unused uv cache

The docs-example test resolves the package by name at runtime, and the
docs build sets its own UV_CACHE_DIR so the setup-uv cache post-step
fails on an empty cache path.


---------
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.

1 participant