8000 Tags · and-elf/omm · GitHub
[go: up one dir, main page]

Skip to content

Tags

Tags

v0.5.0

Toggle v0.5.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
docs(changelog): section v0.5.0 and the previously-unreleased v0.4.0 (#…

…45)

v0.4.0 was tagged but never sectioned in the changelog — its content sat under
[Unreleased] and the compare link still pointed at v0.3.0...HEAD. Section that
content as [0.4.0] - 2026-06-17, and cut the new work merged since (any-port #42,
dual-band #36, topology labels #35, AX3600 target, and the wired-primary backhaul
+ manage_network default changes) as [0.5.0]. A minor bump, not a patch: it adds
features and changes defaults. Compare links updated; the Zero-touch entry's
manage_network note is restored to its 0.4.0 truth (opt-in), since the new
default-on behaviour is its own [0.5.0] entry.

v0.4.0

Toggle v0.4.0's commit message
docs(changelog): record #33 topology/node-removal fixes and the LuCI …

…host theme

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

v0.3.0

Toggle v0.3.0's commit message
release version 0.3.0

v0.0.2

Toggle v0.0.2's commit message
fix(ci): make the release publish step idempotent

`gh release create` hard-fails if a release for the tag already exists, so
re-running the workflow or re-pushing a tag broke with "release already
exists". Create the release only when missing; otherwise upload assets to
the existing one with --clobber.

v0.0.1

Toggle v0.0.1's commit message
test(e2e): match the arch-suffixed .apk filename

The .apk now carries its arch (meshd-<version>-<arch>.apk) so multi-arch
releases don't collide; point the 24.10 e2e target at the x86_64 build
the host packaging step produces. The .ipk target is unaffected (still
meshd_<version>_all.ipk by default).
0