Skip to content

fix: support RW 0.1.36 named documentation identities - #172

Merged
yumike merged 1 commit into
mainfrom
chore/rw-0.1.36
Sep 8, 2026
Merged

yumike merged 1 commit into
mainfrom
chore/rw-0.1.36

Conversation

@yumike

@yumike yumike commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Raise the minimum @rwdocs/core and @rwdocs/viewer versions to 0.1.36.
  • Resolve named homepages from navigation, preserve eligible same-site catalog root links, and keep site setup safe across navigation and asynchronous requests.
  • Use a shared canonical listing projection so search indexing and documentation ownership agree when section identities collide, while retaining independently named descendants.

Upgrade notes

  • Upgrade readers before publishing explicit name metadata.
  • Migrate legacy RW frontmatter and sidecar type fields to kind.
  • Viewer requires Node.js ^22.22.2 or >=24.15.0.
  • Identity changes do not create aliases or automatically migrate existing comments; see README.md for rollout details.

Validation

  • Immutable install, typecheck, lint, workspace formatting, and build passed.
  • 68 test suites / 666 tests passed.
  • Two code-review/fix rounds, parallel test/comment quality reviews, and final human Crit approval completed.
  • Squashed to one changelog-ready commit; its Git tree is identical to the reviewed and tested tree.

Raise the minimum @rwdocs/core and @rwdocs/viewer versions to 0.1.36.

Resolve named homepages from navigation while preserving same-site catalog root links. Align search indexing and documentation ownership with canonical section identities when names collide.

Document reader-first rollout and migration from legacy type metadata to kind.
@yumike
yumike merged commit dec579c into main Sep 8, 2026
1 check passed
@yumike
yumike deleted the chore/rw-0.1.36 branch September 8, 2026 04:30
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