v2.3.2

Updates

• Bump up go module version to something less ancient. Thanks for #37, @juli0604!
• Update all dependencies to latest version and build with go 1.23

v2.3.1

Fixed

• Prometheus functions should now work properly in user-defined templates. Thanks for the report in #33, @cyxou!

v2.3.0

New

• Add support for markdown in messages with the --markdown flag. Thanks for the PR in #32, @thomas-maurice!

Fixed

• The --extended_details flag now works properly by emitting markdown instead of HTML thanks to @thomas-maurice

v2.2.1

Fixed

• Fix bug with template processing to support both single tokens set via config and per-request overrides - thanks for the fix in #30, @IncognitoCoding!

v2.2.0

New

• Add support for complex prometheus template processing - see the README for lots more info! Thanks, @IncognitoCoding for PR #29!

Misc

• Ensure all Printf statements are done via the log package for time formatting consistency.

v2.1.0

New

• Add support for overriding the token per-request and enable use of all prometheus template functions - thanks, @IncognitoCoding for PR #26!

Misc

• The windows/arm combination will no longer be supported in releases due to lack of support in prometheus
• Going forward, the official docker images should now contain CA anchors to avoid unknown authority errors when Gotify is running on HTTPS - thanks for the report in #25, @evandeaubl!
• The build pipeline will build for all os/arch combinations for every commit rather than only on release

v2.0.0

New

• Add support for go text templating and dispatch errors - thanks, @xRy-42 for PR #21!

Possibly Breaking

• The new support for templating can potentially break messages that contain template strings like {{. See PR note for example escape syntax.

v1.0.3

Fixed

• Version output was not properly being set in goreleaser

v1.0.2

Changes for v1.0.2

v1.0.1

New

• No functional changes in the application code are present in this release

Fixed

• The version 1.0.0 Docker image did not work due to an error in the ENTRYPOINT instruction. Thanks for the report in #17, @ngosang!