From 2bfc0154f71696a77c7add3983124bdf0f9f5a0d Mon Sep 17 00:00:00 2001 From: Markus Neusinger <2921697+MarkusNeusinger@users.noreply.github.com> Date: Fri, 4 Sep 2026 00:04:02 +0200 Subject: [PATCH] docs(changelog): the section describes one rollout state again MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit #11207's frontend entry said "the chains are not identical — this one pushes `:latest` only after the promotion, where the API still pushes it alongside the deploy". #11212 is what changed that, so the sentence became false the moment it merged, and the section described two rollout states at once. Past tense, with the PR that closed the gap named rather than a position: the fragments fold in ABOVE the existing bullets at the release cut, so "the entry above" would be wrong now and right later, while "#11212" is true in both. Labelled skip-changelog: this is a correction to an existing entry, not a change worth its own line. It needs the label because the fragment gate compares bullet SETS, so an edited bullet is indistinguishable from an added one — measured, not assumed (`tools.changelog check` answered "[Unreleased] gained a bullet" when this same edit rode along in #11212). Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01UEScQMZFvxxNNyNJYryfa3 --- CHANGELOG.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f2d50a7ce7..1c093da458 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -290,8 +290,9 @@ aggregate instead: an italic *Catalog* line at the end of the version section an traffic** — `app/cloudbuild.yaml` now follows the same candidate-rollout pattern as `api/cloudbuild.yaml`: deploy with `--no-traffic --tag=candidate --revision-suffix=b$BUILD_ID`, smoke the candidate on its tag URL, then `update-traffic` - to exactly that revision (the chains are not identical — this one pushes `:latest` only - after the promotion, where the API still pushes it alongside the deploy). The service + to exactly that revision (the chains were not identical at the time — this one pushed + `:latest` only after the promotion, where the API still pushed it alongside the deploy; + the API caught up in #11212). The service carries the whole crawler path in `app/nginx.conf` — the `$is_bot` map, the `location =` bypasses, the `@seo_proxy` upstream — and that is the file whose breakage served every bot an HTTP 502 for four weeks in 2026 while humans, Plausible and CI all saw a healthy