[lens0021]

CHANGELOG.md and the releases page list every change, generated from the commits, for people tracking the repository. Nothing says what a release means to somebody who uses wikven — and the generated list cannot: it is grouped by commit type, it omits everything .release-please-config.json hides (refactor, test, docs, ci), and it is written in the register of the diff.

Release notes/1.1.0 is that page for the release waiting in #618. Three things a reader of this site would notice get sections — a site that can say where it is, a build that stops on a page it rendered wrong, a licenses page that names the server — and the rest is a list at the bottom.

The draft hatnote

A release page is written before its release exists, so it says so until the release catches up. Template:draft compares the version in the page's own title with {{WIKVENVERSION}}, the version of the Wikven that built the page, and shows the notice only while the first is newer.

Nothing is edited when the release happens. The bake that publishes it is built by it, so the comparison stops being true and the notice stops rendering.

Both halves are wikitext, not Lua. #explode reads a version out of the title and out of {{WIKVENVERSION}}, Template:draft/number turns each into one number so that 1.10.0 sorts after 1.9.0 rather than before it, and one #ifexpr compares them. That needs PFEnableStringFunctions, which ParserFunctions keeps off by default and docs/.wikven.yaml now turns on for this site — the reason it is off is a wiki that takes edits from anyone, and this one is a directory of files rendered once at build time.

A version neither can read is 0, which is what leaves the template a single comparison with no guard around it:

case	named	built	hatnote
the page is about an unreleased version	1001000	1000000	shown
the release lands	1001000	1001000	gone, by itself
a later release	1001000	1002000	still gone
the page is not a release page	0	1000000	none
the build will not say which version it is	1001000	0	shown — a draft shown as published is the failure worth avoiding

Checked

The comparison is simulated against ParserFunctions' own runExplode() and #expr's number reading, over twelve cases: the release landing and the one after it, 1.10.0 against 1.9.0 in both directions, 1.1 and 1.1.0 as one version written two ways, an empty and a non-version {{WIKVENVERSION}}, and two pages that are not release pages. All twelve answer as intended.

Not baked here, so the rendering itself is unproven — the preview job is what will show it, and I will read it when it does.

yamllint passes on the edited .wikven.yaml. Neither page carries <translate> or <languages />, so translate check has nothing to say about them and the language-bars assertion is unaffected.

Two names

The page is titled Release notes and displays What's new. An apostrophe in a title reaches the canonical link percent-encoded, and the head-links bake check looks the file up without decoding it, so What's new/1.1.0 would have failed a check on its punctuation. The words readers see are the ones worth having; the string machines see only has to be safe.

Left for you

• Nothing links either page yet, and neither is in the sidebar, so Module:Sequence.lua writes no navigation row for them. Worth linking from the front page when 1.1.0 ships.
• The prose is a first draft of a judgement call — which changes are worth a reader's attention and which are a line at the bottom. That is yours to move.

🤖 Generated with Claude Code

https://claude.ai/code/session_019ghEx26MRm9V5CnCLrdUQn

---

Generated by Claude Code