twisla/roro9stack
Public Access
1
0
Fork 0
Code Issues 48 Pull Requests 1 Actions Packages Releases 14 Activity

14 Releases 14 Tags

RSS Feed
  • v0.11.0 df2aaddbc8
    Compare

    roro9stack v0.11.0
    CI / build (push) Successful in 14m4s
    Details
    Stable

    twisla released this 2026-10-06 14:39:59 +00:00 | 15 commits to main since this release

    v0.11.0: updates from Gitea (Settings > Firmware checks the project's server, lists the last ten releases and installs one straight into the inactive slot; a daily check announces a newer one; IRC steps aside while the device talks to the server); the Check for updates setting; CI that tests every push to main, builds both firmwares on every pull request and signs and publishes a release for every tag, with coverage and badges

    Files

    • roro9stack-v0.11.0.ota: the signed Update File. Copy it to /updates on the SD card and install it from Settings > Firmware or the Storage App, or push it over Wi-Fi with scripts/ota_push.py.
    • roro9stack-v0.11.0-factory.bin: the whole flash image, for a first install over USB at offset 0.
    • roro9stack-v0.11.0.elf.gz: the symbols, to decode a crash report from this build.
    • SHA256SUMS: checksums of the three.

    Changes since v0.10.0

    • CI: a branch's pushes run nothing, its pull request runs once
    • Updates from Gitea, step 5: the daily check's announcement, the docs, ADR 0009
    • Updates from Gitea, step 4: the Firmware page shows the project's releases
    • Updates from Gitea, step 3: install from Gitea, and IRC steps aside for it
    • Updates from Gitea, step 2: the connection (check and list work on the device)
    • Updates from Gitea, step 1: the model (host-tested)
    • R1 plan: updates from Gitea, the design round (Q162-Q174)
    • R1 plan: pull requests, merged by rebase then a merge commit (Q161)
    • CI: the badges are published from main only
    • CI: a push runs the tests, a pull request also builds the firmware
    • Coverage of lib/ by the host tests, and badges in the README
    • R1 plan: CI and releases are in place
    • R1 plan: CI as built on the container runner
    • CI: jobs run in a container, PlatformIO directly in it, the toolchains in a volume
    • Release build: tags from before Firmware Updates carry no public key to check against
    • R1 plan and ADR 0008: CI signs releases; README section on CI
    • CI: tests and builds on every push, a signed release on a tag (#5)
    • CI: try the runner's label as it is registered
    • CI: a first workflow, to see what the runner gives a job (#5)
    Downloads