Skip to content

chore(docs): refresh packages-index baseline after registry update - #2286

Merged
bpamiri merged 1 commit into
developfrom
chore/refresh-packages-baseline-20260424-164055
Apr 24, 2026
Merged

bpamiri merged 1 commit into
developfrom
chore/refresh-packages-baseline-20260424-164055

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

The wheels-packages registry merged a change that altered the / page of packages.wheels.dev. The committed visual-regression baseline at web/tests/visual-baselines/packages-index.png predated the registry change, so the next unrelated PR would have failed visual-regression on a stale diff.

This PR refreshes only that one baseline so the next PR starts clean.

Generated by the refresh-packages-baseline workflow in .github/workflows/refresh-packages-baseline.yml, triggered by a repository_dispatch: registry-updated event from wheels-dev/wheels-packages.

Test plan

  • visual-regression job passes on this PR
  • Deploy packages job passes (confirms the page the baseline matches is what actually ships)
  • Visual diff of the new baseline vs. the old one contains only the registry change (new package tiles, not layout/typography drift)

🤖 Opened automatically by GitHub Actions.

The wheels-packages registry updated and the rebuilt packages.wheels.dev
index now differs from the committed visual-regression baseline. This is
the expected change — new package tiles on the listing page.

Refreshed automatically by .github/workflows/refresh-packages-baseline.yml
on registry-updated dispatch 104fcb3.
@bpamiri
bpamiri merged commit 3e4f9d9 into develop Apr 24, 2026
@bpamiri
bpamiri deleted the chore/refresh-packages-baseline-20260424-164055 branch April 24, 2026 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant