Skip to content

Deactivate posting schedules for 28 inaccessible destinations - #261

Merged
Fillll merged 1 commit into
masterfrom
maintenance/deactivate-inaccessible-channels
Oct 17, 2026
Merged

Fillll merged 1 commit into
masterfrom
maintenance/deactivate-inaccessible-channels

Conversation

@Fillll

@Fillll Fillll commented Oct 17, 2026

Copy link
Copy Markdown
Owner

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:

  • Verified exactly 28 intended schedule rows were removed, all remaining rows are unchanged, all cron expressions are valid, and maintenance schedules remain present.
  • Release validation against origin/master passed.
  • All 12 release tooling and push-guard tests passed.
  • Full offline application checks are delegated to CI; pytest is not installed in the existing local application environment.

SemVer: patch

@Fillll
Fillll merged commit 621514c into master Oct 17, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants