- PagerDuty incidents are now tracked in the database. This requires an additional database migration if you're an existing users.
- PagerDuty incidents will now be resolved when an incident is resolved in Slack.
- Bug fixes to the existing PagerDuty workflows.
- Minor bug fixes in the UI.
Upgrade Steps
If you're an existing user, you'll have to run the database migrations via make -C backend run_migrations when connected to the database or however you choose to handle the alembic migrations. If you're a first time user, you can ignore this step.