You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
release: 1.4.0 (#35)
Version 1.4.0 makes the chat join link reliable: students who blocked
the bot are known, an undelivered link is retried instead of being lost,
and the first kicks of a new block wait for an admin. After the merge:
tag `v1.4.0` on the merge commit and publish the GitHub Release. While
GitHub Actions cannot run, deploy with `make deploy v=1.4.0`.
## Features
- **Students who blocked the bot.** The bot notices when a student
blocks it (and unblocks it) and stops writing to them. Admins see them:
a «Заблокировали бота» filter and badge on the block page, a badge on
the users page, a column in both xlsx files and on the status sheet.
- **Invite reports.** After a run that sent links or found students who
blocked the bot, the alerts chat gets a summary with their VK links.
Telegram errors are alerted when they start and when they stop.
- **Kick approval.** When a new block becomes the access block, nobody
is removed from the chat until an admin with `sync.run` presses «Убрать
из чата» on the alert. The alert follows the sheet as curators fill it.
After that the block kicks by itself as before.
- **`/start` of a linked student** shows their status with the button to
join the chat.
## Fixes
- A student was counted as invited before the join link reached them; if
it never did (blocked bot, network), they never got it again. Now the
status is set only after delivery, and failed links are retried every 5
minutes. Each invite runs in its own transaction.
- Chat alerts such as «кик из чата ждёт таблицу» came twice when the
sheet sync and the chat job ran at once.
## Migrations
- `users.bot_blocked_at`, nullable.
- `clubs.chat_invites_failing`, false by default.
- `blocks.kicks_approved_at`, `kick_approval_message_id`,
`kick_approval_waiting`, nullable. Blocks that have already started are
approved, so the running block keeps kicking without a button.