feat(container): update ghcr.io/plausible/community-edition (v2.1.5 → v3.0.1) #145
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.
Update Requ 8000 est | Renovate Bot
This PR contains the following updates:
v2.1.5
->v3.0.1
Release Notes
plausible/analytics (ghcr.io/plausible/community-edition)
v3.0.1
Compare Source
This release contains a patch for the migration procedure (fixes https://github.com/plausible/analytics/issues/5319).
Functionally it is equivalent of https://github.com/plausible/analytics/releases/v3.0.0
Upgrade
Update the image used for
plausible
compose.yml
and restart the containers
v3.0.0
Compare Source
Added
exit_rate
metric in the dashboard Exit Pages > Details report28d
and91d
available on both dashboard and in public APIcase_sensitive: false
modifiers in Stats API V2 filters for case-insensitive searches.is not
for goals in dashboard #4983["is", "segment", [<segment ID>]]
filter in Stats APIengagement
event. These are reported assd
ande
integer parameters to /api/event endpoint respectively. If you're using a custom proxy for plausible script, please ensure that these parameters are being passed forward.v
parameter sent with each request.has_done
andhas_not_done
on the Stats API to allow filtering sessions by other events that have been completed.time_on_page
metric is now graphable, sortable on the dashboard, and available in the Stats API and CSV and GA4 exports/importsRemoved
Changed
today
rather thanlast 28 days
. On the next day, the default changes tolast 28 days
.T
still works for last 30 days.7d
and30d
periods do not include today anymorefetch
with keepalive flag as default overXMLHttpRequest
. This will ensure more reliable tracking. Reminder to usecompat
script variant if tracking Internet Explorer is required./api/health
healtcheck is soft-deprecated in favour of separate/api/system/health/live
and/api/system/health/ready
checks-
instead of0
for visit duration, scroll depth when hovering a data point with no visit dataengagement
events sent by plausible tracker script. We still use the old calculation methods for periods before the self-hosted instance was upgraded. Warnings are shown in the dashboard and API when legacy calculation methods are used.date_range
shorthand options like30d
,3mo
.Fixed
visitors.csv
(in dashboard CSV export) vs dashboard main graph reporting different results forvisitors
andvisits
with atime:minute
interval./api/v2/query
no longer returns a 500 when querying percentage metric withoutvisitors
v3.0
Compare Source
Added
exit_rate
metric in the dashboard Exit Pages > Details report28d
and91d
available on both dashboard and in public APIcase_sensitive: false
modifiers in Stats API V2 filters for case-insensitive searches.is not
for goals in dashboard #4983["is", "segment", [<segment ID>]]
filter in Stats APIengagement
event. These are reported assd
ande
integer parameters to /api/event endpoint respectively. If you're using a custom proxy for plausible script, please ensure that these parameters are being passed forward.v
parameter sent with each request.has_done
andhas_not_done
on the Stats API to allow filtering sessions by other events that have been completed.time_on_page
metric is now graphable, sortable on the dashboard, and available in the Stats API and CSV and GA4 exports/importsRemoved
Changed
today
rather thanlast 28 days
. On the next day, the default changes tolast 28 days
.T
still works for last 30 days.7d
and30d
periods do not include today anymorefetch
with keepalive flag as default overXMLHttpRequest
. This will ensure more reliable tracking. Reminder to usecompat
script variant if tracking Internet Explorer is required./api/health
healtcheck is soft-deprecated in favour of separate/api/system/health/live
and/api/system/health/ready
checks-
instead of0
for visit duration, scroll depth when hovering a data point with no visit dataengagement
events sent by plausible tracker script. We still use the old calculation methods for periods before the self-hosted instance was upgraded. Warnings are shown in the dashboard and API when legacy calculation methods are used.date_range
shorthand options like30d
,3mo
.Fixed
visitors.csv
(in dashboard CSV export) vs dashboard main graph reporting different results forvisitors
andvisits
with atime:minute
interval./api/v2/query
no longer returns a 500 when querying percentage metric withoutvisitors
v3
Compare Source
Added
exit_rate
metric in the dashboard Exit Pages > Details report28d
and91d
available on both dashboard and in public APIcase_sensitive: false
modifiers in Stats API V2 filters for case-insensitive searches.is not
for goals in dashboard #4983["is", "segment", [<segment ID>]]
filter in Stats APIengagement
event. These are reported assd
ande
integer parameters to /api/event endpoint respectively. If you're using a custom proxy for plausible script, please ensure that these parameters are being passed forward.v
parameter sent with each request.has_done
andhas_not_done
on the Stats API to allow filtering sessions by other events that have been completed.time_on_page
metric is now graphable, sortable on the dashboard, and available in the Stats API and CSV and GA4 exports/importsRemoved
Changed
today
rather thanlast 28 days
. On the next day, the default changes tolast 28 days
.T
still works for last 30 days.7d
and30d
periods do not include today anymorefetch
with keepalive flag as default overXMLHttpRequest
. This will ensure more reliable tracking. Reminder to usecompat
script variant if tracking Internet Explorer is required./api/health
healtcheck is soft-deprecated in favour of separate/api/system/health/live
and/api/system/health/ready
checks-
instead of0
for visit duration, scroll depth when hovering a data point with no visit dataengagement
events sent by plausible tracker script. We still use the old calculation methods for periods before the self-hosted instance was upgraded. Warnings are shown in the dashboard and API when legacy calculation methods are used.date_range
shorthand options like30d
,3mo
.Fixed
visitors.csv
(in dashboard CSV export) vs dashboard main graph reporting different results forvisitors
andvisits
with atime:minute
interval./api/v2/query
no longer returns a 500 when querying percentage metric withoutvisitors
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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.