Uptime Monitor v3.6.0

Full Changelog: https://github.com/ajjs1ajjs/Uptime-Monitor/commits/v3.6.0

Uptime Monitor v3.5.0

Full Changelog: v3.4.0...v3.5.0

Uptime Monitor v3.4.0

Full Changelog: v3.3.0...v3.4.0

Uptime Monitor v3.3.1

Known issue (documented post-release): this tag points at the exact same commit as v3.3.0 and its binary also reports --version as 3.2.3 instead of the tagged version. No functional changes over v3.3.0.

Fixed in v3.4.0 — please upgrade: https://github.com/ajjs1ajjs/Uptime-Monitor/releases/tag/v3.4.0 (no config/data migration needed).

---

Full Changelog: v3.2.3...v3.3.1

v3.3.0

Known issue (documented post-release): the binary in this release reports --version as 3.2.3 instead of 3.3.0 — the version-string bump was missed in the commit that produced this tag (only internal/** packages were touched; cmd/uptime-monitor/main.go was not). Functionality (Europe/Kyiv timestamps) is unaffected; only the reported version string is wrong. The identical commit was also later re-tagged as v3.3.1, which carries the same issue.

Fixed in v3.4.0 — please upgrade: https://github.com/ajjs1ajjs/Uptime-Monitor/releases/tag/v3.4.0 (no config/data migration needed).

---

Full Changelog: v3.2.3...v3.3.0

v3.2.3

Changed

• *Expanded
  etry_delays\ to [10, 10, 10, 10, 10]* (was [10]) for 5 consistent retries.
• Reverted \max_retries\ default back to 5 (was 3).

v3.2.2

Changed

• Reduced \max_retries\ default from 5 to 3 across config, database schema, example configs and installer for tighter flapping control.