Skip to content

v1.21.3

Choose a tag to compare

View all tags
@loks0n loks0n released this 14 Aug 14:19
· 15 commits to main since this release
v1.21.3
72d7407
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Required if an escalation chain ends in a step that notifies the whole channel.

That step was rejected for any organization without Slack:

POST /api/v1/escalation_policies/
  400 {"detail": "Invalid escalation step type: step is Slack-specific"}

Slack was the only integration that could serve the step when it was added. The Discord integration serves it as well, so the check is now whether any connected chat integration can act on it. A chain ending in that step can be provisioned through the public API and configured in the UI by a Discord-only organization.

Two limits are unchanged:

  • The user group steps still require Slack. They point at a Slack user group, and the task serving them returns early without a Slack team identity.
  • Escalating no longer returns without posting when a route names no Discord role. A route may or may not name one, which is not known when the step is added to a chain, so the message is always posted. The role is mentioned when the route names one.

Full Changelog: v1.21.2...v1.21.3

Assets 4
Loading