Updating

The update badge

When a newer release is out, the status row shows ↑ 0.x.y. Click it (or run "Update modisa" from the palette) to download it and restart the server; your agents come back where they were. Modisa checks at most every six hours.

From the command line

modisa version     # this version, and whether a newer one is out
modisa update      # download, verify its SHA-256, replace this binary
modisa restart     # load it into running sessions

Installed with a package manager

A package manager owns the binary it installed, so modisa update and the update badge give you that tool's command instead (mise upgrade github:manyeya/modisa, or apt or dnf for the .deb and .rpm packages). Run modisa restart afterwards. Agents' hooks call the modisa on your PATH, so they keep working across upgrades.

Verifying a release

Every release file has signed build provenance. gh attestation verify <file> -R manyeya/modisa confirms that this repository's release workflow built the file from a tagged commit.

Channels

stable follows releases. staging follows prereleases built from the staging branch. Set it in [update] channel, or install from it with MODISA_CHANNEL=staging. [update] check = false turns the check off.