chore(docs): refresh blog visual baseline after content change - #3328
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 stale Playwright visual-regression baseline at web/tests/visual-baselines/blog.png after a blog-content merge changed the blog index page (issue #2915). It is a single-file, bot-generated binary change with no code, config, or test-logic surface. Verdict: comment (clean; nothing to block, but the author is wheels-bot so self-approval is not possible).
Correctness
The diff touches exactly one file — web/tests/visual-baselines/blog.png (Bin 121995 -> 126464 bytes) — and nothing else is bundled. The new blob is a valid PNG: PNG image data, 1280 x 800, 8-bit/color RGB, non-interlaced, matching the standard Playwright viewport, so the baseline was captured at the expected resolution. There is no code path to exercise.
One caveat inherent to any binary-baseline refresh: a byte diff alone cannot confirm the screenshot captured a correctly rendered page rather than a broken/half-loaded one. That verification lives in the deploy workflow that generated it (deterministic capture after the content merge), which is the accepted process here — flagging only for awareness, not as a blocker.
Commits
chore(docs): auto-refresh blog visual baseline after content change conforms to commitlint.config.js: valid type chore, suggested scope docs, subject non-empty, not ALL-CAPS, header ≤ 100 chars. Good.
No convention, cross-engine, test-coverage, docs, or security concerns apply to a binary baseline asset.
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.