Update dependency matomo/matomo to ^4.10.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
matomo/matomo (source)	require	minor	^4.5.0 -> ^4.10.1

---

Release Notes

matomo-org/matomo

v4.10.1

Compare Source

Matomo 4.10.1 Changelog

Please use the attached archives for installing or updating Matomo.
The source code download is only meant for developers and will require extra work to install it.

• Latest stable production release can be found at https://matomo.org/download/ (learn more) (recommended)
• Beta and Release Candidates releases can be found at https://builds.matomo.org/ (learn more)

v4.10.0

Compare Source

Breaking Changes

• As access to files like plugin.json might reveal version details, json files will now longer be considered as static files that can be served safely. Therefore json will no longer be included in the list of static file extensions in generated .htaccess files.

v4.9.1

Compare Source

Matomo 4.9.1 Changelog

Please use the attached archives for installing or updating Matomo.
The source code download is only meant for developers and will require extra work to install it.

• Latest stable production release can be found at https://matomo.org/download/ (learn more) (recommended)
• Beta and Release Candidates releases can be found at https://builds.matomo.org/ (learn more)

v4.9.0

Compare Source

Matomo 4.9.0 Changelog

Please use the attached archives for installing or updating Matomo.
The source code download is only meant for developers and will require extra work to install it.

• Latest stable production release can be found at https://matomo.org/download/ (learn more) (recommended)
• Beta and Release Candidates releases can be found at https://builds.matomo.org/ (learn more)

v4.8.0

Compare Source

New config.ini.php settings

• The config setting enable_default_location_provider in Tracker has been added. By setting this option to 0, you can disable the default location provider. This can be used to prevent the geolocator to guess the country based on the users language, if the configured provider doesn't provide any results.

New PHP events

• Added new event Segment.filterSegments. Plugins can use this to filter segment definitions.

v4.7.1

Compare Source

Matomo 4.7.1 Changelog

This Github download (below) is only meant for developers and it will require extra work to install it.

• Latest stable production release can be found at https://matomo.org/download/ (learn more) (recommended)
• Beta and Release Candidates releases can be found at https://builds.matomo.org/ (learn more)

v4.7.0

Compare Source

Deprecated APIs

• The piwik-field and related directives have been converted to Vue and the template-file attribute is now considered deprecated and will be removed in Matomo 5. Instead,
  the component property should be used to add a new form field, it should be an object with two properties that reference a Vue component, plugin and name, where plugin
  is the plugin the Vue component is located in and name is the Vue name of the component's export.

New Change Notifications

• Plugins can now provide a list of changes which will be displayed as part of the "What's New?" menu notification. Learn more about how this works in the developer guide.

v4.6.2

Compare Source

Matomo 4.6.2 Changelog

This Github download (below) is only meant for developers and it will require extra work to install it.

• Latest stable production release can be found at https://matomo.org/download/ (learn more) (recommended)
• Beta and Release Candidates releases can be found at https://builds.matomo.org/ (learn more)

v4.6.1

Compare Source

Due to an issue in our release process (we didn't use the latest build script), we are re-releasing Matomo as 4.6.1.
In this release there is no code change but a change to the "Manifest File integrity list" to prevent a warning in the System check for some users.

v4.6.0

Compare Source

New Framework

• We have begun introducing Vue 3 as the frontend framework to replace AngularJS. You can learn more about it in our developer guide.

New APIs

• New API Methods SecurityPolicy.addPolicy, SecurityPolicy.overridePolicy, SecurityPolicy.removeDirective, SecurityPolicy.allowEmbedPage, SecurityPolicy.disable allow developers to modify or disable the default Content Security Policy. Plugins\Controller has a new member securityPolicy so plugins can use $this->securityPolicy to access these new methods when a custom Content Security Policy is needed.

Breaking Changes

• With the introduction of Vue 3 we are also dropping support for IE11. All new supported browsers are determined by the browserslist tool. Running npx browserslist will list the browsers currently supported.
• When the Ecommerce feature is disabled for a site, then the Live API no longer returns the Ecommerce related visitor properties totalEcommerceRevenue, totalEcommerceConversions, totalEcommerceItems, totalAbandonedCartsRevenue, totalAbandonedCarts and totalAbandonedCartsItems.
• Content Security Policy (added in Matomo 4.4.0) is no longer in Report Only mode by default.

New config.ini.php settings

• The config setting contact_email_address in General has been added. It will be used as contact email address for users. If not defined (default) all email addresses of all super users will be used instead, which equals the behavior it used to be.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: composer.lock

Command failed: docker run --rm --name=renovate_php --label=renovate_child -v "/mnt/renovate/gh/creativecoder/matomo-heroku":"/mnt/renovate/gh/creativecoder/matomo-heroku" -v "/tmp/renovate-cache":"/tmp/renovate-cache" -e COMPOSER_CACHE_DIR -e COMPOSER_AUTH -w "/mnt/renovate/gh/creativecoder/matomo-heroku" docker.io/renovate/php:7.4.29 bash -l -c "install-tool composer 2.3.5 && composer update matomo/matomo --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins"
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Dependency geoip2/geoip2 is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires matomo/matomo ^4.10.1 -> satisfiable by matomo/matomo[4.10.1].
    - matomo/matomo 4.10.1 requires matomo/referrer-spam-list dev-master -> found matomo/referrer-spam-list[dev-master] but it does not match your minimum-stability.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.