Conversation
Bump plugin version to 6.0.0 and require Matomo >=6.0.0-b1,<7.0.0-b1.
* 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.
… Puppeteer 24) (#114) * Update expected UI screenshots for the new headless Chrome (Node 24 / Puppeteer 24) * Update expected UI screenshots for the new headless Chrome (Node 24 / Puppeteer 24) * Re-sync expected UI screenshots for the new headless Chrome after rebase Rendering drift only (identical content, minor line-height/AA shifts) under the new headless Chrome used by the migrated screenshot-testing harness. * 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.
Teal brand screenshots on 6.x-dev plugin base; synced from matomo-org/matomo run 30405694397.
…ature-flag updating screenshots for sparkline feature-flag removal
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>
…lease] The literals 8.1/8.5 drift as soon as core's supported range moves; the aliases resolve centrally in matomo-org/github-action-tests.
PHPStan 2 fails hard on a literal excludePaths entry that matches nothing. The plugin ships no composer.json, so vendor/ never exists; github-action-tests/ only exists during a CI run and is marked optional.
…release] The report header search collapsed from an expanded input into an icon toggle, which shifts every report table up by the height of the old input.
AltamashShaikh
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prepares the Bandwidth plugin for Matomo 6, targeting the new
6.x-devmaintenance branch.plugin.json: version6.0.0,require.matomo>=6.0.0-b1,<7.0.0-b1CHANGELOG.md:6.0.0entrymatomo-tests.yml: PHP matrix on thematomo6_min_php/matomo6_max_phpaliases, MySQL 8.0 / MariaDB 10.6 database matrix, UI job on Node 24 with an explicit databasephpstan.neon:phpVersion8.1; dropped thevendor/exclude (the plugin ships nocomposer.json, so the path never exists and PHPStan 2 fails hard on it) and markedgithub-action-tests/optional, since it only exists during a CI runNo code changes were needed: the Matomo 6 breaking-changes sweep found no use of a removed PHP API, HTTP API method, global function, Less variable or JS/Vue API, and the plugin has no Vue sources, no
Updates/files and no JSON controller actions.Steps to Replicate the Issue
Not applicable — compatibility preparation, no user-facing behaviour change.
Checklist
AI Checklist