diff options
| author | Justin Velluppillai <justin@innocraft.com> | 2021-10-26 05:43:38 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-10-26 05:43:38 +0300 |
| commit | 194d5c35fc1db76b7a32f2980097ca575265efd2 (patch) | |
| tree | 8dd971e350e8d4c5634b674dc4d93cd31c5e6e47 | |
| parent | 7e35a9cbeec451016bcb0157fc95511b0221eca5 (diff) | |
Add new CSP methods to developer changelog (#18198)
| -rw-r--r-- | CHANGELOG.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index 45dc63fed9..2502b12e2e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,10 +10,14 @@ The Product Changelog at **[matomo.org/changelog](https://matomo.org/changelog)* * We have begun introducing Vue 3 as the frontend framework to replace AngularJS. You can learn more about it in [our developer guide.](https://developer.matomo.org/guides/working-with-piwiks-ui) +### 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. ## Matomo 4.4.0 |