chore(docs): refresh blog visual baseline after content change - #3308
Conversation
![wheels-bot[bot]](https://avatars.githubusercontent.com/in/3657588?s=60&v=4){kind=small}
There was a problem hiding this comment.
Wheels Bot — Reviewer
TL;DR — This PR refreshes the committed visual-regression baseline web/tests/visual-baselines/blog.png after a blog-content merge, so downstream web/** PRs stop failing the Visual regression check on a stale-baseline diff (issue #2915). The diff is a single binary asset with a conforming commit message. I verified the new baseline renders the current blog index. Verdict: approve (submitted as a comment because GitHub forbids the bot approving its own PR).
Correctness
The refreshed baseline is consistent with the content it is meant to track. Rendering web/tests/visual-baselines/blog.png shows the Wheels Blog index with the newest post "Wheels 4 Without the Tooling: Two Zips, Zero Dependencies" (July 9, 2026) at the top — exactly the post added in the immediately-preceding content commit 04b347620 docs(web/blog): Wheels 4 Without the Tooling: Two Zips, Zero Dependencies. The baseline therefore reflects real current content, not an accidental or corrupt capture (git show --stat: Bin 119464 to 120146 bytes, 1 file changed).
Commits
chore(docs): auto-refresh blog visual baseline after content change conforms to commitlint.config.js: valid type (chore), optional scope (docs), non-ALL-CAPS subject, header well under 100 chars. The message correctly captures the "why" (baseline drifted after a content change).
Tests / Docs / Security
No code, controller, view, or framework behavior changed — this is a test-fixture asset, so no BDD spec, changelog fragment, or .ai/wheels/ doc update is warranted. No secrets, no user-facing logic. Nothing to flag.
A binary baseline is inherently un-diffable in review; I confirmed intent by rendering the image rather than trusting the filename.
Summary
A blog-content merge changed the blog index page, so the committed visual-regression baseline at
web/tests/visual-baselines/blog.pngis stale. Without this refresh, every subsequentweb/**-touching PR fails the Visual regression check on a deterministic diff until someone refreshes manually (issue #2915).develop's branch protection rejects direct pushes, so the refresh lands through this PR, opened and merged by the deploy run that published the blog change.
🤖 Opened automatically by .github/workflows/web-deploy.yml.