mirror of
https://github.com/kuhyx/signal-bot.git
synced 2026-11-11 21:54:03 +01:00
Krzysztof kuhy Rudnicki
b388f2b249
Some checks are pending
CI / check (push) Waiting to run
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
71 lines
3.0 KiB
Markdown
71 lines
3.0 KiB
Markdown
# Changelog
|
|
|
|
Releases are named after the popes, in order: release *n* is pope *n*. The
|
|
version number is a pure function of that ordinal — see `signal_bot/versioning.py`
|
|
for the two constants and why they are what they are. The short version is that
|
|
Jan Paweł II has to land on 2.13.7, and everything else follows.
|
|
|
|
The bot reads this file. The heading format is load-bearing:
|
|
|
|
```
|
|
## <version> — <pope name>
|
|
- <one change, in Polish, as the group will read it>
|
|
```
|
|
|
|
Add the new section at the top when you bump `RELEASE_ORDINAL`. Anything that
|
|
is not a `##` heading or a `-` bullet under one is ignored, so prose between
|
|
releases is free.
|
|
|
|
**Every release takes the next pope, however small.** A one-line fix consumes
|
|
an ordinal exactly like a feature does; the ladder tracks releases, not
|
|
importance. 0.0.4 and 0.0.5 were both bug fixes. Do not try to squeeze a fix
|
|
out at the current version to "save" a pope -- there are 267 of them.
|
|
|
|
**A version bump is a publish, not a checkpoint.** Restarting the service after
|
|
one posts these bullets into every watched group, including the real one. So
|
|
exercise the feature in a test group — `testbot`, `catbot`, `finaltestbot`,
|
|
each just you and the bot — *before* bumping `RELEASE_ORDINAL`, tagging or
|
|
restarting. To try something at the current version without announcing, leave
|
|
`RELEASE_ORDINAL` alone and restart. Green unit tests and a green
|
|
`scripts/e2e.sh` are **not** sufficient evidence: `e2e.sh` runs against the
|
|
local fake, so it proves the wiring and nothing about how Signal renders the
|
|
result or how the real upstream API behaves. 0.0.3 shipped a `!gekon` that
|
|
passed every gate and posted the same photo every time, because the one thing
|
|
nobody had done was call the real endpoint twice.
|
|
|
|
**Write bullets the group can notice.** The audience is people in a chat, not
|
|
this repo: describe what changes for them. 0.0.1 shipped a bullet about
|
|
`/healthz`, an endpoint bound to 127.0.0.1 that nobody in a Signal group can
|
|
reach, and it was rightly called out.
|
|
|
|
## 0.0.5 — Aleksander I
|
|
|
|
- komendy działają teraz niezależnie od tego, na jakiej klawiaturze je piszesz
|
|
— `!gekon` napisany rosyjskimi literami (albo jako `!g3ck0`) wreszcie
|
|
odpowiada, wcześniej bot go po prostu ignorował
|
|
|
|
## 0.0.4 — Ewaryst
|
|
|
|
- `!gekon` pokazuje teraz za każdym razem innego gekona — wcześniej wrzucał
|
|
w kółko to samo zdjęcie
|
|
|
|
## 0.0.3 — Klemens I
|
|
|
|
- nowa komenda `!gekon` — bot wrzuca losowe zdjęcie gekona; działa też
|
|
`!gecko`, `!geckon`, `!geko`, `!gekony` i `!geckos`
|
|
|
|
## 0.0.2 — Anaklet
|
|
|
|
- bot odpowiada teraz na konkretną wiadomość, cytując ją — w ruchliwej
|
|
rozmowie widać, czyje `!cat` to jest
|
|
|
|
## 0.0.1 — Linus
|
|
|
|
- wersje bota nazywają się teraz imionami kolejnych papieży
|
|
- po aktualizacji bot ogłasza w grupie nową wersję i listę zmian
|
|
- `/healthz` pokazuje wersję i papieża, więc widać co naprawdę działa
|
|
|
|
## 0.0.0 — Święty Piotr Apostoł
|
|
|
|
- bot taki, jaki był przed drabinką papieską: `!cat`, `!dog` i dzienne podsumowanie
|