test(web/blog): refresh visual baseline for new blog post#2487
test(web/blog): refresh visual baseline for new blog post#2487
Conversation
The blog index canary in the visual-regression smoke test pins `/`, which renders the post list. Adding the "Security Hardening in Wheels 4.0" post in 290adef shifted the existing entries down, producing 45,727 pixel diffs (threshold: 200) on every push to develop since. Layout, typography, header, and spacing are unchanged — the diff is purely the new post entry. Baseline replaced with the CI runner's own actual.png so renderer parity is preserved. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM — straightforward visual baseline refresh for the new blog post entry.
Extended reasoning...
Overview
This PR updates a single binary asset, web/tests/visual-baselines/blog.png, used by the visual-regression test for the post index page. The baseline needed a refresh because commit 290adef ("Security Hardening in Wheels 4.0") added a new blog entry, shifting existing entries downward and producing 45,727 pixel diffs against a 200-pixel threshold.
Security risks
None. The file is a PNG used only as a comparison fixture in the visual regression test suite. It is not executed, served to users, or parsed by any production path.
Level of scrutiny
Minimal. This is a mechanical baseline update — a recognized maintenance pattern in visual-regression workflows. The author also took care to source the new baseline from the CI runner's own artifact to preserve renderer parity with the GitHub Actions Chromium environment, which is the correct approach.
Other factors
The PR description is clear about the cause, the scope, and the rationale. The only risk-free way to verify the new baseline is to let the visual-regression CI job run on this PR, which is already in the test plan.
1 participant
Summary
/(post index) failed on develop after the Security Hardening in Wheels 4.0 post landed — 45,727 pixels differ vs. a 200-pixel threshold.blog.actual.pngartifact (from run 25528406944) so renderer parity with the GitHub Actions Chromium environment is preserved.Failing runs this fixes:
Test plan