Update binwiederhier/ntfy Docker tag to v2.36.0 #76
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/binwiederhier-ntfy-2.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v2.35.0→v2.36.0Release Notes
binwiederhier/ntfy (binwiederhier/ntfy)
v2.36.0Compare Source
This release keeps the daily limits across restarts and, with PostgreSQL, shares them between servers, so a visitor gets one daily allowance in total. Each visitor's day now starts at its own time instead of midnight UTC. It also adds an experimental local admin socket.
Features:
/v1/account(stats.reset_at) show when it resets (#2131, see message limits)experimental-listen-admin-unix, off by default) that serves the admin API without credentials to whoever can open it; the shipped systemd unit setsRuntimeDirectory=ntfyfor it (see admin socket)ntfy_db_upper PostgreSQL pool, and health-check the primary like the replicas (#2133)Upgrade notes:
stats_*columns of the user table are zeroed and no longer usedvisitor-email-limit-replenish)base-urlor amessage-size-limitabove 4K is set, so an invalid config that used to start now fails at startup (#1969, thanks to @mikejgray for the contribution)Bug fixes + maintenance:
ntfy pub --wait-pidnow waits for processes owned by other users instead of failing with "not running" (#1710, thanks to @bekoeppel for the contribution)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.
This PR has been generated by Renovate Bot.