Skip to content

Date 6.0.1 for Monday's release and note that JSON objects are decoded #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
snake14 merged 1 commit into from
Oct 6, 2026
Merged

Date 6.0.1 for Monday's release and note that JSON objects are decoded #29

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
## Changelog

### 6.0.1 - 2026-10-06
- Support list configuration values via JSON arrays, e.g. for `trusted_hosts` via `MATOMO_GENERAL_TRUSTED_HOSTS=["example.com","example.net"]`
### 6.0.1 - 2026-10-12
- Support list configuration values via JSON arrays (JSON objects are decoded too), e.g. for `trusted_hosts` via `MATOMO_GENERAL_TRUSTED_HOSTS=["example.com","example.net"]`

### 6.0.0 - 2026-08-10
- Compatibility with Matomo 6
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ List values can be set via encoded JSON arrays:
export MATOMO_GENERAL_TRUSTED_HOSTS='["1.2.3.4","5.6.7.8"]'
```

Any other type of value is used literally. The same applies to JSON values which fail to decode.
JSON objects are decoded too, into keyed arrays. Any other value, including JSON that fails to decode, is used literally.

### Known issues:

Expand Down
Loading