Bump zensical to 0.0.61 - #310
Merged
Merged
Conversation
0.0.61 is a redirects release: anchor redirects, redirect chains resolved
and cycles rejected, so a renamed heading or a split page can keep the
links pointing at it. The redirects plugin is declared here but its map is
empty -- nothing has shipped from this site to redirect yet -- so none of
it fires. The rest of the release loosens two compat validators, for
autorefs settings and for search, and moves the bundled UI to 0.0.29.
Checked by building both locales with 0.0.60 and again with 0.0.61 and
comparing every file, rather than by reading the release notes: 19
pages per locale, and once the generator meta, the bundle hash and one new
__config key are normalised away, every page is identical. No content,
heading, anchor or URL moves. search.json, ja/search.json, sitemap.xml,
ja/sitemap.xml, objects.inv and ja/objects.inv are byte-identical. Both
locales still build --strict with no new warnings, and dependencies and
requires-python are unchanged from 0.0.60.
What the build gains is redirect.json and ja/redirect.json, each holding {}
until a redirect_maps entry exists, and the "redirect" key in every page's
__config that points at them. That is the client half of anchor redirects,
inert while the map is empty.
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
1 participant
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.
Zensical 0.0.61 is a redirects release — anchor redirects, redirect chains resolved, cycles rejected — plus two relaxed
compatvalidators (autorefssettings, search) and the bundled UI at 0.0.29. None of it fires here yet:mkdocs.base.ymldeclares theredirectsplugin with noredirect_maps:, because nothing has shipped from this site to redirect. So the version was checked by building both locales and diffing every file, not by reading the release notes.Same change as cri-middleware/SpriteStudio-Docs#61, going into every repo that shares this pin.
Verified
Built en and ja with 0.0.60 and again with 0.0.61, and compared every file:
<meta name="generator">, thebundle.<hash>.min.jsfilename, and one new"redirect"key in the__configJSON. Normalise those away and every page is identical — no content, no heading, no anchor, no URL moves.search.jsonandja/search.jsonare byte-identical, as aresitemap.xml,ja/sitemap.xml,objects.invandja/objects.inv. The Japanese index is the fragile one — it is segmented into words — and this time it is untouched rather than merely equivalent.redirect.jsonandja/redirect.json, both{}. That is the map the new client-side redirect code fetches; empty, it does nothing.--strict, no new warnings.requires-pythonunchanged from 0.0.60 —zensicalitself is the only line that moves inpip freeze.CI cannot confirm any of this: nothing builds these docs on a pull request, so the local build is the only gate.
Why bump when nothing moves
Because the moment this matters is the first page or heading that moves, and that is a bad moment to find out a release is bad. Anchor redirects are also the first thing in a while these sites have a use for: a heading's anchor is derived from its text, so renaming one silently breaks every inbound link to it, and
redirect_maps:can now carrypage.md#old→page.md#newinstead of only whole-page moves.