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.
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
2 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.
Description
Prepares DeviceDetectorCache for Matomo 6.
6.x-devhas been created as the plugin's Matomo 6 maintenance line, branched in parity from5.x-dev. This PR carries the accumulated Matomo 6 work — the commits that had previously been pushed to or merged intoprepare6xwhile no6.x-devbranch existed — plus the remaining preparation steps:6.0.0and requirematomo >=6.0.0-b1,<7.0.0-b1. The-b1lower bound is required so the plugin is not disabled against a beta core.matomo6_min_php/matomo6_max_phpaliases rather than pinned literals, so they follow core instead of drifting.6.0.0changelog entry.5.x-devremains the Matomo 5 maintenance branch. Nochanges.jsonentry was added — Matomo 6 compatibility is not a user-facing feature.The full Matomo 6 breaking-changes catalogue was swept against the plugin — removed PHP APIs, removed HTTP API methods, removed global functions, changed interfaces, the Monolog 3 / PHP-DI 7 / Symfony 6.4 / php-tracker 4 / PHPUnit 9 dependency upgrades, the
#[JsonResponse]controller contract, removed Less variables and stylesheets, and the removed JS APIs. No code change was required. The only hit is the system test's use ofLive.getLastVisitsDetails, which is unaffected by Matomo 6 restricting the Live API to sites with the visits log enabled — the fixture site has it enabled. Core'smatomo/device-detectorconstraint is unchanged at~6.0between the 5.x and 6.x lines, so the cached parser output stays valid.The plugin has no
composer.json,changes.json,Updates/,phpstan.neonor Vue sources, and no UI tests, so those preparation steps do not apply.Issue No
Part of the Matomo 6 plugin preparation; no separate issue.
Steps to Replicate the Issue
Not applicable — this is a compatibility change with no user-visible behaviour change.
Verified locally against a Matomo 6 checkout (PHP 8.1, MySQL 8.0, Node 24): PHPCS clean, the plugin activates,
core:updatereports no pending migrations, and the unit (3) and integration (28) suites pass.Checklist