Skip to content

Update expected UI screenshots for the new headless Chrome (Node 24 / Puppeteer 24) - #89

Merged
sgiehl merged 2 commits into
prepare6xfrom
dev-20341
Jul 24, 2026
Merged

Update expected UI screenshots for the new headless Chrome (Node 24 / Puppeteer 24)#89
sgiehl merged 2 commits into
prepare6xfrom
dev-20341

Conversation

@sgiehl

@sgiehl sgiehl commented Jul 21, 2026

Copy link
Copy Markdown
Member

Updates the expected UI test screenshots for the new headless Chrome used by the modernized screenshot-testing harness (Node 24 / Puppeteer 24).

This is the submodule counterpart of the core migration PR and must be merged together with it:
matomo-org/matomo#24677

The screenshot changes are rendering drift from the new headless Chrome (identical content, minor line-height/anti-aliasing shifts); each was reviewed against the previous expected before syncing.

Checklist

  • [✔] I have understood, reviewed, and tested all AI outputs before use
  • [✔] All AI instructions respect security, IP, and privacy rules

Match the Node 24 / Puppeteer 24 screenshot-testing stack; the UI job was still pinned to Node 16.
@sgiehl
sgiehl marked this pull request as ready for review July 24, 2026 08:53
@sgiehl
sgiehl merged commit 6d9781f into prepare6x Jul 24, 2026
12 checks passed
sgiehl added a commit that referenced this pull request Aug 9, 2026
… Puppeteer 24) (#89)

* Update expected UI screenshots for the new headless Chrome (Node 24 / Puppeteer 24)

* Run the plugin UI tests on Node 24

Match the Node 24 / Puppeteer 24 screenshot-testing stack; the UI job was still pinned to Node 16.
sgiehl added a commit that referenced this pull request Aug 10, 2026
* Prepare for Matomo 6

Bump plugin version to 6.0.0 and require Matomo >=6.0.0-b1,<7.0.0-b1.

* Run tests on same PHP versions as core (8.1, 8.5)

* Run plugin tests against MySQL 8.0 and MariaDB 10.6 (#87)

* Run plugin tests against MySQL 8.0 and MariaDB 10.6

The workflow inherited the shared action's MySQL 5.7 default, which is below
Matomo's new minimum. Pin the database-backed jobs to the supported floor:
PluginTests now runs a MySQL 8.0 + MariaDB 10.6 matrix, and the UI/JS jobs run
on MySQL 8.0.

* Only upload plugin test artifacts for the MySQL matrix leg

PluginTests runs a MySQL + MariaDB matrix; the upload-artifacts condition
matched both legs and uploaded twice. Restrict the upload to the MySQL leg.

* Update expected UI screenshots for the new headless Chrome (Node 24 / Puppeteer 24) (#89)

* Update expected UI screenshots for the new headless Chrome (Node 24 / Puppeteer 24)

* Run the plugin UI tests on Node 24

Match the Node 24 / Puppeteer 24 screenshot-testing stack; the UI job was still pinned to Node 16.

* Update UI screenshots (#90)

Teal brand screenshots on 6.x-dev plugin base; synced from matomo-org/matomo run 30405694397.

* Update UI screenshots for the report header search

The DataTable search moved from the table footer into the shared ReportHeader
(matomo-org/matomo#24986), which changes every report screenshot.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Add changelog entry for 6.0.0 [ignore_release]

* Use the shared matomo6 PHP version aliases [ignore_release]

The workflow pinned 8.1 / 8.5 as literals, which drift as soon as core
changes its supported range. Resolve them through the central action instead.

* Update PHPStan config for Matomo 6 [ignore_release]

Raise phpVersion to the new PHP 8.1 floor. PHPStan 2 fails hard on an
excludePaths entry that matches nothing, so drop the vendor/ entry (the plugin
has no composer.json) and mark github-action-tests/ optional — it only exists
inside a CI run.

* Update UI screenshots for the collapsed report-header search [ignore_release]

Core now renders the report search as an icon in the shared ReportHeader
instead of an expanded search box, which removes a header row and shifts the
whole treemap up.

---------

Co-authored-by: Thomas ZILLIOX <thomas.zilliox@innocraft.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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