Repository navigation
Releases
Releases · iSlavok/110-Club-Bot
v1.5.0
Version 1.5.0 links club lessons to lessons on the 100points platform and keeps the buttons of sent reminders up to date. After the merge: tag v1.5.0 on the merge commit and publish the GitHub Release. While GitHub Actions cannot run, deploy with make deploy v=1.5.0.
Features
- Platform course of a club. A club gets its 100points course (link or number in the club settings).
- Platform lesson of a lesson. The lesson form picks a lesson of that course, with the suggested one by date. A card of the platform lesson sits next to the form: empty fields are filled from it, differing ones can be taken with «Взять». A Zoom link anywhere in the platform lesson switches the form to «Созвон с куратором» and fills the call link.
- Reminder buttons. Reminders go out with «Подключиться» and «Открыть урок» buttons instead of a link in the text;
/schedulelinks the lessons. - Buttons follow the lesson. Buttons of sent reminders change when the call link or the platform lesson of their lesson changes, «Подключиться» goes 3 hours after the start, a cancelled lesson loses all buttons. Reminders sent before this version get their buttons once, newest first, 50 a minute.
- In the admin panel every platform link opens the platform admin; the student link is only in Telegram. Reading the platform needs
lessons.edit. A rejected platform token sends one alert to the owner.
Build and release
- The platform API client is the private package
points-api(repoiSlavok/100points-api-client, tagv0.1.0). Without it or withoutPLATFORM_TOKENthe bot runs with the integration off. - GHCR images are private now: the release builds the backend with the client (secret
PLATFORM_CLIENT_TOKEN), the deploy logs the server in to GHCR withGHCR_PULL_TOKENonly for the pull. Layers and the uv cache with the client stay out of the Actions cache.
Migrations
clubs.platform_course_id,lessons.platform_lesson_id, nullable.reminders.buttons(jsonb),buttons_checked_at,buttons_lesson_version, nullable.
Before the deploy
- Secrets
PLATFORM_CLIENT_TOKEN,GHCR_PULL_TOKEN; images private. - Server
.env:PLATFORM_TOKEN. - Database backup on the server.
1.4.1
hotfix: 1.4.1 (#36) Hotfix 1.4.1: two admin panel details from 1.4.0. After the merge: tag `v1.4.1` on the merge commit and publish the GitHub Release; while GitHub Actions cannot run, deploy with `make deploy v=1.4.1`. ## Fixes - **Telegram usernames wrapped mid-word** on the users and block pages: the column was 180 px under a fixed table layout, and usernames go up to 32 characters. The column is 240 px now, and a longer username is cut with an ellipsis on one line, whole in the hover title (`TelegramLink`). - **The «заблокировал бота» tooltip** says only when, without the extra «сообщения не доходят». No migrations. Frontend tests, eslint, prettier and tsc pass, run locally.
1.4.0
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.
1.3.0
release: 1.3.0 (#28) Version 1.3.0 gives curators a proper view of who in a block has not reached the chat yet: a page with filters and search, xlsx exports, and a live sheet with the VK links. After the merge: tag `v1.3.0` on the merge commit and publish the GitHub Release. While GitHub Actions cannot run, deploy with `make deploy v=1.3.0`. ## Features - **Block members page.** The members modal is now its own page: funnel filters with counts (in the chat, not in the chat, no bot, bot but not in the chat), search by name, username, Telegram or VK id, sortable columns and the time a student joined the chat. - **xlsx export.** Download the block members with the current filters, and all bot users with the current search. - **Status sheet.** Every 10 minutes the bot rewrites a sheet in the club spreadsheet with the VK links of the access block in three columns: no bot, in the chat, bot but not in the chat. Set «Лист статуса учеников» in the club settings; empty turns it off. The service account needs editor access to the spreadsheet. ## Other - `make deploy v=X.Y.Z`: deploy a tag without GitHub Actions, the images are built locally and loaded on the server over SSH. Migration: `clubs.status_sheet_name`, nullable, no backfill.
1.2.0
release: 1.2.0 (#23) Version 1.2.0 lets admins look up a student's VK from the club chat. After the merge: tag `v1.2.0` on the merge commit and publish the GitHub Release. Publishing builds the images and deploys them. ## Features - **VK lookup in the club chat.** - An admin replies `/vk` to a student's message and gets a card only they can see: the student's name, a link to open the VK page, and the address to copy with one tap. - It also says when the student never wrote to the bot or has no VK linked. - Needs «Просмотр пользователей бота» (`users.view`). - `/vk` is in the chat menu of admins only. Students see no bot commands in groups any more, and the bot stays silent if they type it. ## Fixes - The flaky lesson form test that failed about half of the CI runs. No migrations.
1.1.0
release: 1.1.0 (#20) Version 1.1.0: messages to the club chat written in the admin panel. After the merge: tag `v1.1.0` on the merge commit and publish the GitHub Release. Publishing builds the images and deploys them. ## Features - **Messages to the club chat.** - «Сообщение в чат» on the club reminders page opens an editor with Telegram formatting: bold, italic, underline, strikethrough, spoiler, links, inline code, code blocks and quotes. A preview shows the message as the chat will. - It goes to the reminders topic now or at a set time, and can be changed or cancelled until then. - Messages appear in the reminders feed and are sent, retried and alerted on like reminders. - The new permission «Сообщения в чат клуба» (`messages.send`) is needed to write them; it is not given to existing roles. Includes a migration: `reminders.text`, nullable `reminders.lesson_id`, two check constraints.
1.0.4
Features
- Reminder previews. The lesson form shows the text of any reminder as typed, before saving: an eye on every offset and on «remind now».
- Remind now. The lesson card sends a lesson or homework reminder to the chat at the next minute, after showing its text.
- Usual times. Settings keep the usual lesson start (16:00) and homework deadline (23:59); picking a day in an empty picker sets them.
- Admins in every club. Owners and active admins get into any club chat by request, are never removed, and see every club in
/statusand/schedule. - Block members sorting by VK id, bot user or chat state; those who linked the bot come first by default.
- Database access over SSH. PostgreSQL listens on
127.0.0.1:${PG_PORT:-5432}on the server for a database client through an SSH tunnel.
Fixes
- Today is marked in date pickers; the users table keeps its column widths; long club settings values no longer overlap; a lesson card shows all its reminders; reminder actions are icons; the schedule command reads «Расписание».
Includes a migration: app_settings.default_lesson_time and default_homework_time.
1.0.3
hotfix: 1.0.3 (#17) Patch release 1.0.3. After the merge: tag `v1.0.3` on the merge commit and publish the GitHub Release; publishing deploys it. ## Admin panel logo - The club logo is the favicon and the home-screen icon (`public/favicon.png`, `public/apple-touch-icon.png`). - It sits next to the title on the login page and before the club name in the header (`shared/ui/Logo`).
1.0.2
Fixes
- VK profile without names. VK returns some existing profiles with the id alone. The bot took that for an outage and told the student VK was down, so the page could not be linked. Such a profile is now accepted; the confirmation shows the page link without a name.
1.0.1
Fixes
- One join link per chat. Telegram lets a bot create only about 20 invite links a minute per chat, so personal links made the start of a big block take most of an hour and paused the bot. A club now keeps one join-request link; the bot approves the student who asked if they have access. Forwarded links still let nobody else in.
- Flood protection. Private messages and button presses are limited per user (five in a row, then one a second); the excess is dropped before it touches the database.
Includes a migration: chat_accesses.invite_link moves to clubs.chat_invite_link.