Repository navigation
Deactivate posting schedules for 28 inaccessible destinations - #261
Merged
Merged
Conversation
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
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.
Stop scheduling 28 Telegram destinations whose bot access no longer supports delivery: 12 have explicit posting restrictions or bot removal, and 16 return “member list is inaccessible.” Read-only API checks reconfirmed these conditions before the change.
Remove only their entries from own.cron. Keep channel definitions and delivery history so maintainers can restore schedules after admins request reactivation in the Town Hall topic and restore bot access. This maintenance change uses a patch release because it retires failing schedules without changing the application interface or storage format.
Validation:
SemVer: patch