Repository navigation
Conversation
snake14
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
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 the plugin for Matomo 6.
plugin.json: version5.0.1→6.0.0, andrequire.matomo→>=6.0.0-b1,<7.0.0-b1. The-b1lower bound is required so the plugin is not disabled against a beta core.
CHANGELOG.md: new6.0.0entry..github/workflows/phpcs.yml: the PHPCS job ran on PHP 7.4, which is below Matomo 6's PHP 8.1 floor.Bumped to
8.1. This workflow callssetup-phpdirectly, so it does not go through the centralmatomo6_*alias resolver.No code changes were needed. The Matomo 6 breaking-changes catalogue was swept against this repository —
removed PHP APIs, removed HTTP API methods, removed global functions, changed interfaces, the
Monolog 3 / PHP-DI 7 / Symfony 6.4 / php-tracker 4 dependency upgrades, the
#[JsonResponse]controllercontract, removed Less variables and stylesheets, removed JS/Vue APIs, and the Jest → Vitest migration —
with no hits. Both integration points were checked against core 6.x directly: the
Tracker.getJavascriptCodeevent and the$codeImpl['protocol']key it writes are unchanged incore/Tracker/TrackerCodeGenerator.php, andPiwik\DI::decorate()still exists with the same decoratorsignature under PHP-DI 7.
The plugin declares no
composer.json,Updates/,vue/src,phpstan.neonor test workflows, so thecorresponding preparation steps do not apply.
Both commits are marked
[ignore_release]: this only establishes Matomo 6 compatibility and nothing canbe released for Matomo 6 until core ships.
Issue No
Related to the Matomo 6 plugin preparation effort.
Steps to Replicate the Issue
./console plugin:activate ForceSSLsucceeds../console core:updatereports no pending migrations../console config:get --section=General --key=force_sslreturns"1", confirming the configdecorator still applies on Matomo 6.
./vendor/bin/phpcs --standard=phpcs.xmlpasses on PHP 8.1.Checklist