chore(main): release 1.1.0 by github-actions[bot] · Pull Request #618 · chaotic-ground/wikven

github-actions · 2026-09-01T23:40:26Z

🤖 I have created a release beep boop

1.1.0 (2026-09-20)

Features

have a bake say where its time went (#719) (d9d56e5)
have serve say where the site it is serving can be read (#733) (b1c42da)
have the binary introduce itself rather than Caddy (#734) (fd4d889)
let a bake keep the extensions and skins it fetched (#723) (ec65354)
let a site say where it will be published (#621) (6e458fd)
let WikvenFailOnCategories name the categories a build must find no page in (#661) (89d4726)
name the server a binary build ran on, on the licenses page (#617) (d68b969)
refuse a translation carrying a tag that belongs to its source page (#675) (d0bfe72)
say which address a page is published at, and where its translations are (#658) (002260c)
write a sitemap for a site that says where it is published (#623) (b0ad0a1)

Bugfixes

answer a caller that asked for a whole URL with one (#630) (effaada)
answer a change to an English page in English alone (#715) (7d2bc8e)
give a picture named in a page's metadata an address that resolves (#648) (a2c3b32)
give the settings page the sentence written for it (#753) (6615b96)
let a picture named in a page's head be told from one in its body (#671) (2aa57ca)
let Citizen's preferences panel keep its own spacing (#708) (904775d)
let the downloaded tarball go when the fetch does not (#695) (0595e40)
measure a sitemap against both the caps it has to be inside (#669) (a12295f)
report a run the standalone binary's build died in (#665) (6f77af3)
stop handing a reader the address of the machine that built the site (#638) (eac411d)
stop loading skins the site never asked for (#662) (99a8f9b)
stop shipping a Caddy module wikven cannot use (#619) (e186a3d)
stop the preview answering for an address the site does not have (#650) (18e6b01)
stop the translation drain spinning on a queue that gives nothing (#739) (b93aeef)
tell a source editor only about translations that fail the check (#718) (38d5640)
wait for the page before filling in the skins section (#649) (d615e2a)

Performance

give the image the gmp its base conversions keep asking for (#742) (16e8f39)
keep the job queue on the database the build already has open (#736) (5b79453)
let a bake's boots share what the first one compiled (#741) (bfb9a14)
let the binary's bake share its compiled PHP too (#743) (228d783)
let the wiki's own database sync the way the three beside it do (#725) (bb7a8d2)
offer Translate only the languages the source is written in (#730) (fd74048)
parse the pages beside each other before importing them (#728) (619fb47)
spare the translation units a description they will never show (#737) (cd45597)
stop purging a cache a bake does not have (#735) (bcbb842)
stop rebuilding translation stats a bake goes on to recompute (#722) (500cb23)
stop rendering translation pages the build renders again (#729) (e3d40d4)
stop running two jobs a static export has no reader for (#726) (c866061)
tag the base page ready without writing it again (#738) (b672785)

This PR was generated with Release Please. See documentation.

Split out of #623, which now stacks on this. ## The defect `SiteConfig::lint()` reads a site's `WikvenSiteUrl` through `SiteUrl`, and ran twenty lines above the `require_once` that loads it. Any site that actually set the value fataled at `LocalSettings` time: Fatal error: Uncaught Error: Class "MediaWiki\Extension\Wikven\SiteUrl" not found in /var/www/html/WikvenSettings.php CI never saw it. The path is behind `$siteUrl !== ''` and no test site set one, so the only setting #621 added was broken on its only non-default path with all 26 checks green. `docs/.wikven.yaml` now names the documentation site's own URL. That is what stops this recurring: the path is in every bake CI runs, and it fills `$wgCanonicalServer` besides, so an absolute URL MediaWiki or an extension builds names the right host instead of `localhost`. ## Why this is a chore and not a fix The defect was introduced by #621, and #621 has not been released — it is sitting in the pending 1.1.0 (#618). Nobody running 1.0.0 ever had this bug. `.release-please-config.json` shows `fix` under a visible "Bugfixes" section, so typing this as a fix would put a line in 1.1.0's notes describing a defect no released version carried. `chore` is hidden, which is the right answer for repairing unreleased work. The commit message says the same, so the reasoning survives the squash. ## Checked locally Built with the released binary over this working tree: - A site setting `WikvenSiteUrl` — reproduced the fatal, then confirmed the build completes and writes its pages. - `$wgCanonicalServer` comes out as `https://chaotic-ground.github.io` where `WikvenSiteUrl` is `https://chaotic-ground.github.io/wikven/` — the host half, path left to wikven. - `phpcs` (60 files), `mago format --check`, `mago lint`, `yamllint` all clean. `phpcs` now runs here, which it did not for the three lint failures earlier in this stack: `phpcsstandards/phpcsextra` was installed but its sniff path was not registered, so every `Universal.*` reference errored out. Registering `installed_paths` fixed it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_019ghEx26MRm9V5CnCLrdUQn --- _Generated by [Claude Code](https://claude.ai/code/session_019ghEx26MRm9V5CnCLrdUQn)_ Co-authored-by: Claude <noreply@anthropic.com>

…use it (#676) `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.com/claude-code) https://claude.ai/code/session_019ghEx26MRm9V5CnCLrdUQn --- _Generated by [Claude Code](https://claude.ai/code/session_019ghEx26MRm9V5CnCLrdUQn)_ --------- Co-authored-by: Claude <noreply@anthropic.com>

#744 landed as `feat:`. It is not one: `.tf/` says how GitHub is configured, and a reader of the release notes has no wiki that behaves differently for it. release-please read the label it was given and put it under **Features** in #618. ## What can and cannot be corrected A merged commit's type cannot be changed — `main` takes no rewrite, and release-please offers nothing that retypes an earlier commit. `Release-As:` is the one footer that reaches back, and it would change nothing here anyway: ten other `feat:` commits since 1.0.0 already settle the minor bump, so 1.1.0 is 1.1.0 either way. The mistake cost a changelog line, not a version. What the configuration does offer is `exclude-paths`, which drops a commit whose every file sits under one of the named paths — before the type is ever read. So this is not a correction of one commit but of the rule that let it through: nothing under `.tf/` reaches a release again, however it is labelled. ## Effect release-please re-reads the range on every run, so #618 loses the entry on the next one. Of every commit since 1.0.0, exactly one touches nothing but `.tf/` — #744 — so that is the only line that moves. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_019ghEx26MRm9V5CnCLrdUQn --- _Generated by [Claude Code](https://claude.ai/code/session_019ghEx26MRm9V5CnCLrdUQn)_ Co-authored-by: Claude <noreply@anthropic.com>

github-actions · 2026-09-20T05:06:03Z

🤖 Created releases:

v1.1.0

🌻

github-actions Bot added the autorelease: pending label Sep 1, 2026

github-actions Bot force-pushed the release-please--branches--main branch 2 times, most recently from 5539ffc to cd542f2 Compare September 2, 2026 17:34

lens0021 mentioned this pull request Sep 2, 2026

chore: repair the settings load order WikvenSiteUrl needs #624

Merged

github-actions Bot force-pushed the release-please--branches--main branch 14 times, most recently from b8cf1cd to 56720a2 Compare September 6, 2026 11:47

lens0021 mentioned this pull request Sep 6, 2026

docs: say what a release brought, in the words of somebody who would use it #676

Merged

lens0021 marked this pull request as draft September 6, 2026 13:15

github-actions Bot force-pushed the release-please--branches--main branch 8 times, most recently from 6aa9cbf to b22fbb5 Compare September 8, 2026 14:50

github-actions Bot force-pushed the release-please--branches--main branch 14 times, most recently from cfdf47d to c0686c0 Compare September 10, 2026 15:34

lens0021 mentioned this pull request Sep 10, 2026

ci: keep the repository's own settings out of the release notes #746

Merged

github-actions Bot force-pushed the release-please--branches--main branch 6 times, most recently from c61f076 to 2c28d5a Compare September 17, 2026 13:05

lens0021 marked this pull request as ready for review September 20, 2026 05:03

chore(main): release 1.1.0

3e3449b

github-actions Bot force-pushed the release-please--branches--main branch from 2c28d5a to 3e3449b Compare September 20, 2026 05:03

lens0021 merged commit c2e15e2 into main Sep 20, 2026

lens0021 deleted the release-please--branches--main branch September 20, 2026 05:05

github-actions Bot added autorelease: tagged and removed autorelease: pending labels Sep 20, 2026

Navigation Menu

Repository navigation

chore(main): release 1.1.0 - #618

chore(main): release 1.1.0#618
lens0021 merged 1 commit into
mainfrom
release-please--branches--main

github-actions Bot commented Sep 1, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

github-actions Bot commented Sep 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🤖 I have created a release beep boop

1.1.0 (2026-09-20)

Features

Bugfixes

Performance

Uh oh!

github-actions Bot commented Sep 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

github-actions Bot commented Sep 1, 2026 •

edited

Loading