Skip to content

Nimstead Assure 0.3.1

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 28 Oct 14:40
· 6 commits to main since this release
b640d87

Release channels. Releases now come in three channels: preview (earliest, may break), beta (feature-complete, being proven) and stable (public). Your server follows one and also takes anything more stable. There's no beta or stable release yet, so set NIMSTEAD_UPDATE_CHANNEL=preview in .env to keep getting updates; the default is stable. Agents are unchanged (still 0.2.0), so machines need nothing.

Upgrade from 0.3.0: 0.3.0's Settings doesn't show preview releases, so run deploy/update.sh on the Docker host (it checks the signature, backs up the database and rolls back if needed). Then add NIMSTEAD_UPDATE_CHANNEL=preview to .env and restart with docker compose up -d. From 0.2.0: git fetch --tags && git checkout v0.3.1 && docker compose up -d --build, then rerun the install command on each machine once.

Added

  • Release channels: preview, beta and stable. Each release's signed manifest says its channel, and a server follows one (NIMSTEAD_UPDATE_CHANNEL, default stable), taking its channel and anything more stable. Settings shows the channel, and deploy/update.sh installs the newest release the channel allows. A tag is released as preview; promoting it re-signs the same commit for beta or stable with your approval. 0.3.0 is a preview release.
  • Docker base images and the PostgreSQL image are pinned by digest, and Dependabot proposes updates to them and to the pinned GitHub Actions.
  • web/scripts/readme-shots.mjs regenerates the README screenshots from the real-hosts demo.
  • Each GitHub release's notes are its CHANGELOG section, not a pointer to the file.

Changed

  • "Not reporting" alerts wait one report cycle after the server itself was down, so an outage doesn't page about every machine.

Full list: CHANGELOG.