v3.6.0

• feat(alerting): Added Google Chat alerting provider #234 - @kpolischuk
• feat(alerting): Allow specifying a different username for email provider #231 - @tmoitie
• fix(ui): Prettified event timestamps #243 - @TwiN
• style(ui): Improved login UI design - @TwiN
• build(docker): Support more platforms for latest tag #238 - @kkhan01
• chore: Updated front-end dependencies - @TwiN
• chore: Fixed a few typos in the documentation #241 - @ItsAzaria

v3.5.0

• feat(ui): Updated project logo - @TwiN
• feat(ui): Status page headline and link to open when clicking on the logo can now be configured #232 - @TwiN
• feat(security): Added support for OpenID Connect #228 - @TwiN
• feat(security): Implemented security.basic.password-bcrypt-base64 in favor of security.basic.password-sha512 #233 - @TwiN
• feat(alerting): Added Opsgenie alerting provider #214 - @vinicius73
• feat(metrics)!: Updated metrics exposed #223 - @TwiN
• fix(alerting): Added group in alert messages #221 - @TwiN
• fix: Improved endpoint and alert validation #221 - @TwiN
• refactor: Moved from io/ioutil to io and os packages #211 - @Juneezee
• docs: Fixed several typos #215 #216 #217 - @ianagbip1oti
• docs: Added missing maintenance configuration in main configuration table #226 - @zeylos
• perf: Replaced GitHub's PNG logo for a SVG - @TwiN
• style: Default to dark mode - @TwiN

v3.4.0

• Implement email alerts #117
• Fixed caching issue with svg chart

v3.3.6

Changed license from MIT to Apache 2 #203

v3.3.5

Fixed paging issue with Postgres #202

v3.3.4

• Events now display the number of days ago rather than the number of hours if the event happened more than 72 hours
• Fixed icon_url for Mattermost alerts
• Updated TwiN/health to v1.1.0
• Updated front-end dependencies

v3.3.3

• Deprecated storage.file in favor of storage.path #197
• Deprecated persistence for storage of type memory #198
• Minor data savings improvement

v3.3.2

Restructure storage package

v3.3.1

• Handled issue caused by #192 for users using storage of type memory with a file specified
• Made minor changes needed for upcoming gatus.io

v3.3.0

Renamed service to endpoint #191 #192

THIS CHANGE IS BACKWARD COMPATIBLE

I've been wanting to rename service to endpoint for a while now.
service is confusing, and it doesn't align well with features I want to implement in the future.

As such, I finally decided to make the move.

What you need to know

For most people, all you need to do is replace services: by endpoints: in your configuration file, but here's a full break down of the changes that may impact you.

Endpoint changes

All /api/v1/services/* routes will continue working until v4.0.0 for the sake of backward compatibility, but should be replaced by /api/v1/endpoints/*.

This includes badges.

Configuration changes

services has been renamed to endpoints, but the former will continue being supported until v5.0.0. This is a pretty big breaking change, and I want people to have enough time to migrate.

Before:

services:
  - name: website
    url: "https://twin.sh/health"
    conditions:
      - "[STATUS] == 200"

After:

endpoints:
  - name: website
    url: "https://twin.sh/health"
    conditions:
      - "[STATUS] == 200"

If you continue using services in your configuration, there will be a warning logged in the console pointing to this issue

Storage

SQLite and Postgres

If you are using a storage of type sqlite or postgres, the data in the old tables will not be migrated. I considered automatically migrating the data, but decided that it was not worth the trouble given that currently, the retention period is very short.

That being said, the old tables are not going to be automatically deleted, in case you are using said data for other purposes.

Here is a list of the old table names and their replacements:

• service -> endpoints
• service_event -> endpoint_events
• service_result -> endpoint_results
• service_result_condition -> endpoint_result_conditions
• service_uptime -> endpoint_uptimes

---

If you have any questions, please ask them in #191