Release: develop -> main - #4148
Merged
Merged
Conversation
…ATION_CHAT_ID (#4142) The Telegram escalation target chat id was only settable through the runtime POST escalation/telegram-bind call, which writes a DB setting. Add an optional SUPPORT_ESCALATION_CHAT_ID env var: a non-secret chat id (useless without the bot token) that the deployment can pin, so the target becomes versioned, reviewed configuration instead of manual runtime state. When set it takes precedence in getBoundChatId(); when unset the DB binding still applies.
github-actions
Bot
requested review from
TaprootFreak and
davidleomay
as code owners
July 9, 2026 10:07
TaprootFreak
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automatic Release PR
This PR was automatically created after changes were pushed to develop.
Commits: 1 new commit(s)
Checklist