Update ntfy to v2.24.0

Co-authored-by: Kai Chappel <kaichappel@users.noreply.github.com>
This commit is contained in:
Kai ChappelandKai Chappel authored and GitHub committed 2026-06-05 16:51:24 +10:00
1 parent 09b514bc88
commit e78b62804f
2 files changed
+5 -5

No files matched your search

+1 -1
View File
@@ -8,7 +8,7 @@ services:
PROXY_AUTH_ADD: "false"
app:
image: binwiederhier/ntfy:v2.23.0@sha256:b32b4221a64ec2e7c000f0782b2feef24022e1a09a24e531640f4cbba6cfa1e6
image: binwiederhier/ntfy:v2.24.0@sha256:f8a9b104313b87cc24ae4f775f39e6328205b57dff6ede3eaf098a91e5d79f59
user: "1000:1000"
restart: on-failure
stop_grace_period: 1m
+4 -4
View File
@@ -3,7 +3,7 @@ id: ntfy
name: ntfy
tagline: Send notifications to your phone or desktop via scripts from any computer, and/or using a REST API
category: automation
version: "2.23.0"
version: "2.24.0"
port: 13119
description: >-
ntfy (pronounced notify) is a simple HTTP-based pub-sub notification service. It allows you to send notifications to
@@ -52,13 +52,13 @@ gallery:
- 2.jpg
- 3.jpg
releaseNotes: >-
This update adds new per-visitor rate limits for topic creation to help mitigate topic enumeration and squatting attacks.
This update fixes a security issue where SQLite-backed access control rules could match topics case-insensitively (for example, a rule for `secret` could also match `SECRET`).
It also improves security by removing unused web app dependencies and restricting local file previews in the publish dialog to safe image types.
It also adds an optional in-memory access-control cache for high-volume servers, improves PWA token refresh, and fixes the `rel` attributes on auto-linked notification URLs.
Full release notes can be found at https://github.com/binwiederhier/ntfy/releases/tag/v2.23.0
Full release notes can be found at https://github.com/binwiederhier/ntfy/releases/tag/v2.24.0
dependencies: []
path: ""
defaultUsername: umbrel