Fixed — the self-updater could re-run on every restart and repeat its notice
The "already updated" fact lived only in an environment marker. That marker
survives os.execv, but not a restart from any other source — a service
manager with Restart=always, the watchdog, or a manual restart all clear it.
So a bridge that could not come up cleanly after an update re-ran the updater on
every restart and re-sent the "updated" notice each time.
This release adds a disk marker alongside the environment marker, so the fact
outlives the process lineage. Update notices are also de-duplicated, so a
repeated notice is not delivered twice.
If you install from PyPI, this is the fix you want — the previous published
build (v0.9.6) does not contain it.
Also in this release
- Mirrored messages are sanitized before truncation. Previously a long
message could be cut mid-marker, leaving a half-written suggested-reply tag,
and bold markers could end up unpaired (a stray opening**).
Not changed in this release
The "am I a pip-managed install?" check still decides from the install path
alone (site-packages / dist-packages in the resolved path). A source
checkout that happens to live under such a directory is still treated as
pip-managed. That is a separate issue and is not addressed here.
Upgrade
pip install --upgrade codex-telegram-bridgeFull Changelog: v0.9.6...v0.9.7