Repository navigation
Conversation
…elease Older releases move to their own page. Old anchors on the upgrading page go on to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ndings Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
eizedev
marked this pull request as draft
November 22, 2026 15:07
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The upgrading page had grown to 1,658 lines. Update steps, the newest release and every older release were mixed, and GitHub showed the raw
{ #anchor }after each heading. This rewrites it from scratch.What changes:
docs/getting-started/upgrading.mdhas two parts. "Update an installation" has one short section per way of installing. "From 0.8 to 0.9" has a four-step summary at the top, the breaking changes with who and what to do, then the other changes that can break a test, a script or a client. Items with nothing to do are left out. They stay in the changelogs.docs/getting-started/upgrading-older.mdis new. It holds the steps for 0.8.1 and earlier, moved without content changes. It is in the nav under Upgrading.<span id>inside the heading. That renders cleanly on GitHub and on the site, and the strict build checks them.overrides/main.htmlgets a small script: on a page whose front matter setsanchors_moved_to, a link to an anchor the page no longer has goes on to the same anchor on that page. Every anchor that changelogs, release notes, docs and the server's messages link to exists on one of the two pages.docs/reference/localisation.mdanddocs/versioning.mdpoint to the new page where needed.Checked:
zensical build --strict,check-readme-links.js,node --test tests/*.test.js, Vale on the new page, and a neutral review of the rendered page as a React/element user, a server operator and a core/CLI developer.Places checked for descriptions of this page: README, PRODUCT.md, CONTRIBUTING.md, AGENTS.md, docs/versioning.md, docs/embed/index.md, the getting-started and reference pages that link it, the package READMEs and changelogs.
🤖 Generated with Claude Code