🎉 Version 1.2.1
What's Changed
- [Fix] Ensure robust Apprise notifications and prevent loops
This commit resolves a critical bug that could cause notification loops and enhances the Apprise integration for better flexibility and reliability.
Key changes include:
-
Decoupled State and Notification: Fixed a major bug by updating a repository's
lastSeenReleaseTag
before a notification is sent. This prevents all notification loops, which was especially problematic if the Apprise service was temporarily unavailable. -
Flexible Apprise URL Configuration: The application now correctly handles the
APPRISE_URL
, whether it's a base URL (e.g.,http://host
) or includes a full path with a configuration key (e.g.,http://host/notify/key
). This makes the Apprise integration more flexible. -
Simplified Apprise Test Notification: The test notification for Apprise now uses a basic Markdown payload, ensuring compatibility with a wider range of notification services and preventing false negatives during testing.
Solves Issue #17
Full Changelog: v1.2.0...v1.2.1