Skip to content

docs(changelog): the section describes one rollout state again #11218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MarkusNeusinger merged 2 commits into from
Sep 3, 2026
Merged

docs(changelog): the section describes one rollout state again #11218

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2bfc015
docs(changelog): the section describes one rollout state again
MarkusNeusinger Sep 3, 2026
5726c6b
Merge remote-tracking branch 'origin/main' into docs/changelog-rollou…
MarkusNeusinger Sep 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading