update-screenshots

To update screenshot baselines from a CI artifact, download the newest screenshot-diff artifact using an authenticated gh CLI, review the markdown diff report, replace the repository baselines, and commit the changes with Git LFS handling.

Local screenshot tests often fail in CI due to platform differences like fonts, rendering, or DPI. Syncing baseline images directly from the GitHub Actions artifact removes this local rendering noise by using the CI-generated images as the source of truth.

You need an authenticated GitHub CLI, access to the screenshot-diff CI artifact, and Git LFS-aware commit and push handling to successfully download, review, and replace component fixture screenshot baselines.

To safely commit and push large screenshot baseline files updated from CI, use a Git LFS-aware workflow that includes the required LFS push handling to ensure the refreshed screenshot assets are published successfully to the repository.

Yes, you can review what changed in screenshot test failures before accepting new baselines. The workflow surfaces the markdown diff report from the CI artifact so you can inspect exactly what visual changes occurred.

Git LFS is required if your repository stores large screenshot assets. The workflow includes the required LFS push handling to ensure that baseline image replacements and commits are published successfully without hitting file size limitations.