chore(deps): update ghcr.io/plausible/community-edition docker tag to v3 #8229
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.
This PR contains the following updates:
v2.1.5->v3.1.0Release Notes
plausible/analytics (ghcr.io/plausible/community-edition)
v3.1.0Compare Source
Added
include.trim_relative_date_range- this option allows trimming empty values after current time forday,monthandyeardate_range valuestransformRequestfunction to change event payloads before they're sentcustomPropertiesfunction hook to derive custom props for events on the flyplausible.init({ ...your overrides... })- this can be unique page-by-page@plausible-analytics/trackerESM module is available on NPM - it has near-identical configuration API and identical tracking logic as the script and it receives bugfixes and updates concurrently with the new tracker scriptRemoved
Changed
event.props.pathto be explicitly defined when tracking: it is set to be the same asevent.pathnamein event ingestion; if it is explicitly defined, it is not overridden for backwards compatibilityday,monthandyearperiodsbounce_ratemetric in Entry Pages breakdownFixed
visitorsandvisitsper hour, count visits in each hour they were active inv3.0.1Compare 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
plausiblecompose.yml
and restart the containers
v3.0.0Compare Source
Added
exit_ratemetric in the dashboard Exit Pages > Details report28dand91davailable on both dashboard and in public APIcase_sensitive: falsemodifiers in Stats API V2 filters for case-insensitive searches.is notfor goals in dashboard #4983["is", "segment", [<segment ID>]]filter in Stats APIengagementevent. These are reported assdandeinteger 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.vparameter sent with each request.has_doneandhas_not_doneon the Stats API to allow filtering sessions by other events that have been completed.time_on_pagemetric is now graphable, sortable on the dashboard, and available in the Stats API and CSV and GA4 exports/importsRemoved
Changed
todayrather thanlast 28 days. On the next day, the default changes tolast 28 days.Tstill works for last 30 days.7dand30dperiods do not include today anymorefetchwith keepalive flag as default overXMLHttpRequest. This will ensure more reliable tracking. Reminder to usecompatscript variant if tracking Internet Explorer is required./api/healthhealtcheck is soft-deprecated in favour of separate/api/system/health/liveand/api/system/health/readychecks-instead of0for visit duration, scroll depth when hovering a data point with no visit dataengagementevents 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_rangeshorthand options like30d,3mo.Fixed
visitors.csv(in dashboard CSV export) vs dashboard main graph reporting different results forvisitorsandvisitswith atime:minuteinterval./api/v2/queryno longer returns a 500 when querying percentage metric withoutvisitorsConfiguration
📅 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.
This PR has been generated by Renovate Bot.