github nicholas-fedor/shoutrrr v0.25.0

one hour ago

What's Changed

Shoutrrr v0.25.0 adds Discord mentions and threads, XMPP server lookup through SRV records, Twilio API keys, and display names in SMTP addresses. It also changes how HTTP services treat redirects and replies, so a send counts as delivered only when the provider accepted it.

Redirects and Delivery

  • A service's default HTTP client follows a redirect only on the same host name and never from HTTPS to HTTP. It also refuses a redirect that would resend a POST as a GET without its body, except a 303. A custom HTTP client keeps its own redirect policy.
  • A send counts as delivered only on a 2xx status. A redirect the HTTP client did not follow, or any other status, fails the send instead of reporting success. A Slack webhook reply with a status other than 200 fails too.
  • A Join push that the Join API refuses now fails instead of reporting success.

Discord

  • Only the mentions listed in the new mentions key ping. An @everyone, @here, user, or role mention written in the message text no longer pings anyone. Earlier releases let a channel webhook ping @everyone from the text.
  • Each send waits for Discord to confirm the message was saved, and a failed send reports Discord's own error message.
  • A webhook request is retried only when it could not connect, so a slow answer is never posted twice.
  • The new thread_name key creates a thread in a forum or media channel.

Gotify

  • Only application tokens are accepted. A client token fails when the URL is read, since Gotify 3 cannot send with one without an application ID.
  • The token is sent in the X-Gotify-Key header by default. Set useheader=no to keep it in the query.

PagerDuty

  • An acknowledge or resolve event needs a dedup_key, and it sends only the alert's key and action.
  • The new title key becomes the event summary, and the message then goes to custom_details.message.
  • An event over 512 KB, details that are not a JSON object, and text: entries in contexts fail before the request.

MQTT

  • Each sender connects with its own client ID by default, so two senders on one broker stop taking over each other's session. A broker that accepts only known client IDs needs clientid set.
  • A message larger than the broker's maximum packet size fails instead of being dropped by the broker.

XMPP

  • The server certificate is checked against the domain of the JID. A URL whose JID names another domain than its host needs a certificate for the JID's domain.
  • A URL without a port whose host is the JID's domain finds the server through its SRV records, and falls back to the host when there are none.

SMTP

  • Sender and recipient addresses can carry display names, such as Jane Doe <jane@example.com>.
  • An address that is not a valid email address, such as a bare root, is rejected when the URL is read. So is a recipient whose display name holds a comma.

Generic

  • Settings in the URL query match in any letter case, so Method=GET sets the method. A webhook parameter that shares a setting's name in another case is now read as that setting, and needs the __ prefix to reach the webhook. A URL that names one setting in two spellings is rejected.
  • contenttype now applies to sends without a template. Without it, such a send still goes out as text/plain.
  • A title in the URL reaches the payload under the title key.

Twilio

  • The new apikey key sends with an API key, with its secret as the password.
  • Only a sender of MG followed by 32 hexadecimal characters is sent as a Messaging Service. An alphanumeric sender ID is sent as written.
  • An empty message or one over 1600 characters fails before the request.

Other Services

  • Bark sends a badge only when it is positive, so a push no longer clears the app's notifications. A negative badge is rejected.
  • Telegram sends with the Bot API 7.0 fields and shows the title in every parse mode. A thread ID that is not a positive integer is rejected.
  • An ntfy topic behind a base path is published to the base path, so a server hosted at the root answers with an error instead of reading the topic as a sequence ID.

Deprecations

The following items are deprecated in this release. See the Deprecations documentation page for more information.

URL Settings

Service Deprecated Replacement
Bark category None

Go API

Package Deprecated Replacement
bark Config.Category None
bark PushPayload.Category None

Commits

Features

Fixes

Full Changelog: v0.24.0...v0.25.0

Don't miss a new shoutrrr release

NewReleases is sending notifications on new releases.