nightly 2026-10-14

Under the hood: Vue 3.5.44 (24 fixes in server rendering, hydration and the scheduler), checked page by page against the previous build — every page renders identically. The onion gateway moves to rustls 0.23.46, which fixes four low-severity advisories filed today. No visible change to the site.

nightly 2026-10-13 — a link to a heading lands on it

A link to a README heading lands on it. Opening a link like /projects/nanna/about#api-key-invalid sometimes landed a few pixels past the heading in Chromium-based browsers. On a long README, about one load in five did, and it got worse on a busy machine, sometimes leaving the heading tucked behind the masthead. It now lands on the heading every time.

README images hold their place after a deploy. Right after the site restarted, a slow badge host could leave a README's images without reserved space until the next refresh, so the text around them shifted as they loaded. The site now falls back to the size it measured last time, and the fallback snapshot keeps those sizes too.

/healthz and the status page report how README images were sized: measured, kept from the snapshot, or unsized.

marked 18.1.1 renders the READMEs and posts. Its output is byte-identical to before on every one of them.

Also in this release: the site's own browser checks catch the heading miss reliably now. A page that stops responding fails within three minutes and says where it was, instead of holding a CI job for fifteen.

nightly 2026-10-12 — a reload puts you back

• A reload puts you back where you were, on every page. Reloading /projects, a blog, /news or a project page with its README folded used to jump to the top; only the home page came back. In Chrome, Back from another site did the same. Now each lands where you left it.
• An open README stays exactly where you were reading. A reload no longer slips 2 px further each time.
• Coming back is a jump, not a scroll. In Chrome, a reload used to scroll down from the top over half a second; it now lands at once, as it already did in Firefox.
• The offline fallback snapshot now carries Skidbladnir v1.4.3.

nightly 2026-10-11 — the masthead gets out of the way

• Heading links land in view. A link to a README heading, #download, or the home page's sections now stops just below the masthead instead of underneath it — in every browser, with or without script.
• Keyboard focus is never hidden behind the masthead (WCAG 2.2 Focus Not Obscured).
• Zoomed and sideways windows get their screen back. Below 30rem of height (a phone held sideways, a desktop at 400% zoom) the masthead scrolls away with the page rather than staying on top.
• Windows contrast themes: the Basic Automation mark and every project wordmark stay visible on dark themes.
• Printing gives a flat page: no glass effects, no [copy] buttons.
• Tor Browser at "Safest": with SVG off, a project's name still reads as its page heading instead of small text above an empty box.
• The onion service is now checked from outside every six hours by a fresh Tor client that passes the abuse gate like a visitor (npm run probe:onion).

nightly 2026-10-10 — Back puts you back

• Back, Forward and reload jump straight back to where you were reading. They used to scroll smoothly from the top of the page, and on a slower device could stop a line short. Links to headings still scroll smoothly.
• The server log records the visitor's address as Cloudflare reports it (cfIp). Before this, every clearnet request was logged with Docker's gateway address.
• Nuxt 4.6.1.
• More reliable checks: the browser accessibility pass now runs once the page has stopped scrolling, and a failed navigation check prints a frame-by-frame trace.

nightly 2026-10-09 — a README that keeps your place

The project pages' folded README now behaves the way a reader expects, in Firefox and Tor Browser as well as Chromium.

• Back, Forward and reload keep your place in a README. Opening a project's README, moving to its blog tab and pressing Back used to bring you back to a folded README thousands of pixels from where you were. It now reopens at the same spot, and a reload does too.
• Links to a README heading land on it in Firefox and Tor Browser. A link like /projects/onyums/about#how-onyums-compares used to stop at a folded README in Firefox with the heading hidden.
• README images no longer make the page jump. Their sizes are known before they load, so nothing below them moves as they arrive. Skidbladnir's README used to shift by almost 700 px.
• No dead buttons with JavaScript off. At Tor Browser's "Safest" level the [copy] buttons could do nothing; they are now hidden there. Everything else on the site already works without script.
• vue-router 5.4.
• Behind the scenes: the accessibility pass and a new navigation check now run in Firefox as well as Chromium, on every pull request.

nightly 2026-10-08 (2) — the onion service heals itself

• The onion service recovers without taking the site down. If the Tor onion service hasn't been reachable for an hour, the site restarts its onion gateway in place, at most hourly. The clearnet site keeps serving throughout. Previously the cure was restarting the whole container.
• Onion outages are in the log. onion.unreachable is logged when the service becomes unreachable and hourly while it lasts. onion.restarting is logged when the gateway is restarted, and onion.recovered when the service is reachable again. Until now an outage was only visible to whoever asked /healthz.
• A gateway that won't stop on request is now force-stopped after 9 seconds rather than waited on forever.
• Refreshed offline fallback data, and a build-tool update (harfbuzzjs 1.6.3) with no change to the served font.

nightly 2026-10-08 — Nuxt 4.6

• The site now runs on Nuxt 4.6.0, which carries the framework's fixes for its internal error route being reachable from outside and for unhandled error details reaching the error page. Pages, routes and status codes are unchanged.
• A development-only dependency (shell-quote) was moved past a published advisory; nothing that reaches visitors changed.
• CI and the release workflow run on current, Node 24 versions of their GitHub Actions.

nightly 2026-10-05 (2) — a README can't stall a page

• README rendering can no longer stall the server: marked 18.1.0 and the site's own README patterns now run in linear time on hostile input.
• Copy buttons announce that they copied, and when the clipboard is refused they select the text and say so.
• Response headers: x-powered-by is gone and Cross-Origin-Opener-Policy is set.
• A failed request's log line now says who asked (user agent, referrer, web or onion).
• The dependency audit covers the code shipped to the browser, not only the server; accessibility checks run on axe-core 4.14.

nightly 2026-10-05 — no holes when one piece fails to refresh

• No more missing sections during upstream hiccups. When a project's README, release list or crates.io numbers fail to refresh, its page keeps showing the last copy the site fetched instead of dropping the section. /status says which pieces it is showing that way.
• Skidbladnir's screenshot is re-cut from the app's current README. It is now served at a versioned URL, so a future re-cut reaches returning visitors straight away instead of up to a day later.
• Every server log line is JSON, including failed upstream fetches (event: "upstream.fetch_failed"), so docker logs basicautomation-site | jq reads all of it.
• The offline fallback snapshot is refreshed (Skidbladnir v1.4.2).
• Under the hood: type checking is back on vue-tsc, and two dev dependencies got patch updates.