v1.21.0
Forum tags for status and severity
Where a forum has tags with these names, a post is tagged with its status and its severity, and the tags are kept current:
Firing Acknowledged Silenced Resolved
Critical Warning Info
Decoration around the name is ignored, so 🔥 Firing, Resolved ✅ and Status: 🔥 Firing all match the firing status. Tags that do not exist are not applied. A forum with only status tags behaves as it did before.
Severity renamed
A route's severity was alert or warning. It is now critical, warning or info, matching the values used in alerting labels. A firing card reads by its severity (🚨 red,
MSG91 SMS provider
A phone provider for MSG91, selected with PHONE_PROVIDER=msg91 and configured by MSG91_AUTH_KEY, MSG91_SENDER_ID and MSG91_TEMPLATE_ID. These are live settings, so they can be corrected in Settings without a restart.
SMS only. MSG91 has no calls and no verification service, so the verification code is generated and checked by OnCall. The flow template must be registered with a single variable named content or otp, which receives the message text.
Upgrading
No migration is required. A route saved as warning still means warning. A route saved as alert reads as critical, which is what it meant, so rendering does not change. The route editor shows critical for such a route and writes critical the next time the route is saved.
A forum set up against an earlier version has a tag named Alert, which no longer matches anything. Rename it to Firing or Critical, then re-connect the channel. Until then its posts keep the tag they were last given, because an unmatched name leaves a post's tags alone rather than clearing them.
Full Changelog: v1.20.0...v1.21.0