Repository navigation
v0.1.1
makeitMD gets a panel. The product boundary moved deliberately: /start now opens
two tabs instead of answering with a sentence and no way forward. Still no
settings.
Changed
/startnow opens a panel instead of answering with one sentence. Two
tabs and no more: How it works, and an About card carrying the version and
commit the running process reports on/healthz, the rendering it uses, the
repository, the licence and the admin.Backis the only navigation, every
tab edits the same message rather than posting another one, and there is still
nothing to configure. The greeting itself is unchanged.- Commands are published per scope instead of globally. The private list
is/start — Open the makeitMD panel; the group list is one/start
registered as ephemeral, so a person on a Bot API 10.3 client who types it in
a group gets a private link back to the direct chat and the group sees nothing
at all. An older client cannot send an ephemeral command, so the bot has no
message it is entitled to answer privately and stays silent rather than
replying in front of everyone -- which reads as a dead bot, and will be the
common case until clients catch up. The default
scope, where the old globalStart the botentry lived, is cleared. Nothing
is offered in a chat where it would do nothing. - One versioning and release document for the whole family.
docs/versioning.md
anddocs/releases.mdare now byte-identical across every Asterfield
repository apart from two clearly marked sections: this repository's own
version line, and the surface where a change here breaks something. They spell
out what each of the three numbers means, what the-alpha.Nsuffix counts,
when alpha becomes beta and when it is legitimate to skip to rc or run a
pre-release in production. - Pre-releases are now tagged on
dev, notmain. Only stable versions are
tagged onmain, on the merge commit fromdev.release.ymlhad no branch
check at all before, so a tag pushed from any branch would publish; it now
refuses a tag that is not on the branch its channel is published from.
Earlier pre-releases were tagged onmainunder the previous rule; they are
left as they are. github.com/FreshLabDev/tgmoves tov0.0.1-alpha.7. It carries one fix:
a preflight probe is marked as a probe, so the404 method not foundit
expects stops being counted and logged as a transport failure. All four bots
on the shared client now run the same version.
Added
-
docs/releases.mdgained a Deploying section, andAGENTS.mdpoints at it.
Releasing was documented; deploying was not, in any repository in the family —
the process stopped at "deploy it" and never said how. That gap mattered more
after the stacks moved from building on the host to pulling a published image,
because the procedure changed on the same day. The section names this stack's
host directory, its env file, the variable that selects the image, the networks
it needs, and what a rollback actually is. -
internal/buildholds the version, commit and build date the linker stamped
in./healthzand the About card read the same value, so the panel cannot
report a build that is not the one answering. -
deploy/ws04/compose.yaml, the production stack, pulling the image the
release workflow publishes to GHCR. The stack on the host built its own image
from a working copy, so what served users was not the artifact CI had tested,
scanned and published, and nothing on the host could say which commit it came
from.MAKEITMD_IMAGEhas no default: an unset one stops the stack instead of
quietly starting something else.