Update binwiederhier/ntfy Docker tag to v2.34.0 #67

Merged

mathieu merged 1 commit from renovate/binwiederhier-ntfy-2.x into main

2026-10-24 22:45:23 +00:00

Renovate_Bot commented

2026-10-24 22:00:38 +00:00

Collaborator

This PR contains the following updates:

Package	Update	Change
binwiederhier/ntfy (source)	minor	`v2.32.0` → `v2.34.0`

Release Notes

binwiederhier/ntfy (binwiederhier/ntfy)

`v2.34.0`

Compare Source

This release prepares the experimental cluster to run behind load balancers: nodes drain on shutdown instead of dropping all of their clients at once, ntfy can listen on several addresses, and access changes reach every node. It also fixes a revoked or deleted user keeping some of their subscriptions, on every server.

Features:

Allow several comma-separated addresses in listen-http, so a load balancer can hold more than ~63k connections to one ntfy node
Cluster nodes drain on shutdown: an active node withdraws (stops being ready), then turns read-only and closes its subscriber connections gradually (experimental-cluster-drain-delay, experimental-cluster-drain-duration), so its clients move to the other nodes without a reconnect storm (experimental, see draining on shutdown)

Security:

End all of a user's subscriptions when their access to a topic is reset or the user is deleted: only the first one was ended, so the others kept receiving the topic's messages (#1845, thanks to @gigioneggiando for reporting)
In an experimental cluster, tell the other nodes when access changes (e.g. a reservation or a revoked permission), so they reload their access cache and disconnect subscribers who lost access; the access cache reload also catches changes made elsewhere, e.g. by the ntfy access CLI, and now runs every 67 seconds instead of 87

Bug fixes + maintenance:

Fix a deadlock when ending subscriptions (reserving a topic with live subscribers, revoking access, deleting a user) while debug logging or log-level-overrides is on: the subscriptions' topic stayed locked for good
Fix a data race when log-level-overrides changes (e.g. on a config reload with SIGHUP) while the server logs

`v2.33.1`

Compare Source

This release builds ntfy with Go 1.27.3 (security fixes, including rejecting the compromised eMudhra intermediate CAs), and adds monitoring for the experimental cluster: each node's view of its peers, per-peer and database connection pool metrics.

The v2.33.0 release had an issue that made it crash on older CPU architectures. The v2.33.1 release fixes that (see #2092).

Features:

Show each cluster node's view of its peers with ntfy cluster status, /v1/cluster/status on the cluster listener, and per-peer metrics, so a link that only works in one direction is visible (experimental clustering, see cluster status)
Export PostgreSQL connection pool metrics (ntfy_db_pool_*: connections in use, and queries that waited for a free connection, per pool), to size pool_max_conns (see PostgreSQL)

Security:

Build with Go 1.27.3, which includes the security fixes of Go 1.27.2 (crypto/tls, net/http, html/template and others) and 1.27.3 (crypto/x509: certificate chains through the compromised eMudhra intermediate CAs are rejected)
Reject phone number verification unless Twilio confirms the code as approved, instead of accepting any successful response
Ignore duplicate topics in a subscription and limit a subscription to 150 topics, so a single request cannot replay the same topic's cache over and over

Bug fixes + maintenance:

Count published messages from every cluster node: each node adds its own publishes to the stored total instead of the leader overwriting it with its own count (experimental clustering)
Fix "Illegal instruction" crash of the amd64 binaries on CPUs without x86-64-v3 (AVX2/BMI2), by building releases on Ubuntu 24.04 again (#2092, thanks to @frank-bg for reporting)

`v2.33.0`

Compare Source

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.

If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [binwiederhier/ntfy](https://ntfy.sh/) ([source](https://github.com/binwiederhier/ntfy)) | minor | `v2.32.0` → `v2.34.0` | --- ### Release Notes <details> <summary>binwiederhier/ntfy (binwiederhier/ntfy)</summary> ### [`v2.34.0`](https://github.com/binwiederhier/ntfy/releases/tag/v2.34.0) [Compare Source](https://github.com/binwiederhier/ntfy/compare/v2.33.1...v2.34.0) This release prepares the experimental cluster to run behind load balancers: nodes drain on shutdown instead of dropping all of their clients at once, ntfy can listen on several addresses, and access changes reach every node. It also fixes a revoked or deleted user keeping some of their subscriptions, on every server. **Features:** - Allow several comma-separated addresses in `listen-http`, so a load balancer can hold more than \~63k connections to one ntfy node - Cluster nodes drain on shutdown: an active node withdraws (stops being ready), then turns read-only and closes its subscriber connections gradually (`experimental-cluster-drain-delay`, `experimental-cluster-drain-duration`), so its clients move to the other nodes without a reconnect storm (experimental, see [draining on shutdown](https://docs.ntfy.sh/config/#draining-on-shutdown)) **Security:** - End all of a user's subscriptions when their access to a topic is reset or the user is deleted: only the first one was ended, so the others kept receiving the topic's messages ([#1845](https://github.com/binwiederhier/ntfy/pull/1845), thanks to [@gigioneggiando](https://github.com/gigioneggiando) for reporting) - In an experimental cluster, tell the other nodes when access changes (e.g. a reservation or a revoked permission), so they reload their access cache and disconnect subscribers who lost access; the access cache reload also catches changes made elsewhere, e.g. by the `ntfy access` CLI, and now runs every 67 seconds instead of 87 **Bug fixes + maintenance:** - Fix a deadlock when ending subscriptions (reserving a topic with live subscribers, revoking access, deleting a user) while debug logging or `log-level-overrides` is on: the subscriptions' topic stayed locked for good - Fix a data race when `log-level-overrides` changes (e.g. on a config reload with SIGHUP) while the server logs ### [`v2.33.1`](https://github.com/binwiederhier/ntfy/releases/tag/v2.33.1) [Compare Source](https://github.com/binwiederhier/ntfy/compare/v2.33.0...v2.33.1) This release builds ntfy with Go 1.27.3 (security fixes, including rejecting the compromised eMudhra intermediate CAs), and adds monitoring for the experimental cluster: each node's view of its peers, per-peer and database connection pool metrics. *The v2.33.0 release had an issue that made it crash on older CPU architectures. The v2.33.1 release fixes that (see [#2092](https://github.com/binwiederhier/ntfy/issues/2092)).* **Features:** - Show each cluster node's view of its peers with `ntfy cluster status`, `/v1/cluster/status` on the cluster listener, and per-peer metrics, so a link that only works in one direction is visible (experimental clustering, see [cluster status](https://docs.ntfy.sh/config/#cluster-status)) - Export PostgreSQL connection pool metrics (`ntfy_db_pool_*`: connections in use, and queries that waited for a free connection, per pool), to size `pool_max_conns` (see [PostgreSQL](https://docs.ntfy.sh/config/#postgresql)) **Security:** - Build with Go 1.27.3, which includes the security fixes of Go 1.27.2 (`crypto/tls`, `net/http`, `html/template` and others) and 1.27.3 (`crypto/x509`: certificate chains through the compromised eMudhra intermediate CAs are rejected) - Reject phone number verification unless Twilio confirms the code as approved, instead of accepting any successful response - Ignore duplicate topics in a subscription and limit a subscription to 150 topics, so a single request cannot replay the same topic's cache over and over **Bug fixes + maintenance:** - Count published messages from every cluster node: each node adds its own publishes to the stored total instead of the leader overwriting it with its own count (experimental clustering) - Fix "Illegal instruction" crash of the amd64 binaries on CPUs without x86-64-v3 (AVX2/BMI2), by building releases on Ubuntu 24.04 again ([#2092](https://github.com/binwiederhier/ntfy/issues/2092), thanks to [@frank-bg](https://github.com/frank-bg) for reporting) ### [`v2.33.0`](https://github.com/binwiederhier/ntfy/compare/v2.32.0...v2.33.0) [Compare Source](https://github.com/binwiederhier/ntfy/compare/v2.32.0...v2.33.0) </details> --- ### 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. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

Renovate_Bot added 1 commit

2026-10-24 22:00:38 +00:00

Update binwiederhier/ntfy Docker tag to v2.34.0 1671c41784

mathieu force-pushed renovate/binwiederhier-ntfy-2.x from 1671c41784 to 50d9721865

2026-10-24 22:43:46 +00:00

Compare