chore(release): v2.24.0 - #142
Merged
Merged
Conversation
Bump every version reference from 2.23.2 to 2.24.0 (backend __version__, frontend package.json and lock, both image-pinning compose files, prereq.sh, README and USER_MANUAL callouts, the docs/index.html footer stamp). scripts/check_version_sync.py passes. Docs for the release: - README gains a Features bullet for dated message timestamps (#140). The station-positions bullet (#141) landed with that PR and is unchanged. - USER_MANUAL section 3 gains a Timestamps paragraph covering the same behaviour, including the midnight rollover. - docs/legality.html moves its reviewed date to August 2026: the #positions section was added after the July review. No transmission behaviour changed in this release, so the compliance content itself is untouched. The docs/index.html feature grid is deliberately left alone — it is a curated marketing grid, not a changelog, and the positions card is already there.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release prep for v2.24.0. Nothing but version stamps and docs — no behaviour changes.
Version bump
2.23.2 → 2.24.0 in all eleven places across nine files:
backend/__init__.py(what
/healthand the UI report),frontend/package.json+package-lock.json×2,docker-compose.images.yml,docker-compose.portainer.yml(header comment, bothimage pins, the commented
-cudaexample),prereq.sh, the README and USER_MANUALcallouts, and the
docs/index.htmlfooter stamp.python3 scripts/check_version_sync.py→All version references agree: 2.24.0, andgit grep 2.23.2outsideCHANGELOG*comes back empty.What's in the release
and APRS on RF (KISS TNC), a map panel with a screen-reader-friendly list peer, offline
tile pack at
/data/tiles, and a nearest-first list on e-ink kiosks. Its README bullet,USER_MANUAL § 34 and § 22d, and the site's module card all landed with that PR.
rolls over at midnight without a reload. This PR adds its README bullet and a
Timestamps paragraph in USER_MANUAL § 3, which were never written.
docs/legality.html
Reviewed date moved July → August 2026. The
#positionssection was added after theJuly review. The compliance content is unchanged — this release alters no transmission
behaviour, and every position source is receive-only.
Not done
docs/index.html's feature grid is untouched by design — curated marketing, not achangelog, and the positions card is already in it.
Manual smoke for #141 is still un-run: Docker stack, a real tile pack, real
Meshtastic/APRS hardware, and the
/displaye-ink branch. Automated suites are green(backend 2026, frontend 1221,
tsc -p tsconfig.build.jsonclean), but nothing in thisfeature has touched hardware.