Prepare for v1.0.1 release
main: Return 500 when publishing a notification fails
When publishing to ntfy failed, the webhook handler only logged the error
and still responded with 200. Alertmanager treats that as a successful
delivery and never retries, so an alert can be lost silently while ntfy is
briefly unavailable.
Respond with 500 instead, so that Alertmanager's retry mechanism re-delivers
the notification. Notifications that were published successfully are cached
and skipped on the retry, so re-delivery does not duplicate them.
just: Fix helm linting II
Give a working example of `update-notification`
You must specify a value here, otherwise ntfy-alertmanager crashes
with the following:
```
ERROR Failed to read config error="directive \"update-notification\": want 1 params, got 0"
```
Prepare for v1.0.0 release
redis: Update deprecated function call
Support templates
The body of the notification can now be rendered from a template.
readme: Add note about markdown formatting
Fix bugs in multialert message format
Support markdown in multi-alert mode as well
docker: Read version from justfile
docker: Build smaller binaries
Compile with ldflags "-w" and "-s".
"-w" removes DWARF debugging information
"-s" removes the symbol table