changelog/v<major>/<major>.<minor>.x/<version>.md for each of the 42 releases from v1.0.0 to v4.7.1, and changelog/beta/ for pre-releases (none has been published; its README says how one would be filed). CHANGELOG.md becomes the index: what the layout is, [Unreleased] exactly as it was, and a table per major version (version, date, edition) that links each file. Each file is its section, copied byte for byte except that its heading is the file's H1 (so the sub-headings move up one level, outside code fences), relative links gain ../../../ so they name the same repository paths, and the --- separators between sections are gone. Checked by reversing all three changes on every file and comparing with the original section: 40 of 40 equal. Two releases had no section: v1.0.0 (its GitHub release notes, which the changelog pointed to as "Initial stable") and v1.1.3 (its tag message). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.5 KiB
2.5 KiB
v4.5.1 – 2026-10-27 (The "Speed Bump" Edition)
The site's Worker now limits how fast one address can call it, behind
Cloudflare's own rate-limiting rule at the edge. Nothing changes for readers,
the apps or the pipeline: every limit sits far above what they send. The
desktop and Android apps stay at 2.3.0, with no new build. Repo
public-facing version 4.5.0 → 4.5.1.
🔐 Security
- Rate limits in the Worker, one budget per surface. Per address and per
minute: the catalogue API 240 requests (loading the whole catalogue takes
about 16), the image proxy 600, the other public API routes 120, the human
check 20 (a person sends one a day) and the admin surface 300. Past a limit
the Worker answers
429 Too Many RequestswithRetry-After: 60until the minute is up; the apps can read that answer, where they would otherwise have seen a network error. An IPv6 address counts by its /64, the block one subscriber is normally given. Cloudflare keeps these counts per server, so they stop a client that keeps its connection open, as browsers and most scripts do; one that reconnects for every request is left to the edge rule, which counts exactly. They are ceilings for abuse, never quotas. The limits are bindings inweb/wrangler.jsoncand change by pull request. - Two layers, the edge first. The zone's rate-limiting rule still refuses a burst before the Worker runs, at no cost, and is the only limit on the pages themselves; the Worker adds the one-minute window the Free plan's 10-second rule cannot, and keeps holding if that rule is changed. If the Worker's limiter is ever unavailable, requests go through rather than fail.
- The recommended edge rule now covers the whole site except the hashed
JavaScript and CSS bundles, at 250 requests per 10 seconds per address. That
is about twice what a first visit sends once the offline cache fills in
(counted from the build: 110 to 130 requests in a few seconds). Applying it
is a Cloudflare dashboard change, described in
docs/SECURITY_SETUP.md§3a.
📚 Docs
docs/SECURITY_SETUP.md§3 describes both layers, how to check each one withcurl, and the Free-plan rule budget as it stands (one of one rate limiting rule, four of five custom rules).CLAUDE.mdrecords the layer's rules: it fails open, is not logged, keeps a 60-second period and an account-uniquenamespace_idper binding, and needs a budget for any prefix the Worker runs first for.