Bricklogger 0.2.2

Bricklogger 0.2.2

Upgrading

• bricklogger update upgrades Bricklogger and its plugins from PyPI:
  update status shows what there is, update core upgrades Bricklogger as
  far as the installed plugins allow, update <type> one plugin, and
  update all everything together. The new version checks the configuration
  before anything is restarted, the previous versions are put back when it
  does not hold, the systemd units are brought up to date, and the units that
  run are restarted. Run the install script once to get 0.2.2; from there on
  sudo bricklogger update all takes over.
• The daemon looks for newer releases once a day and names them in status
  and the daily summary mail. updates: {check: false} in daemon.yaml
  turns the look off on a network with no way out.
• The web interface's Plugins screen shows the newest releases, with an
  Update per plugin and a Check now.

Fixed

• A configured type whose plugin is not installed no longer stops the
  daemon. Its instances are failed, with a warning that names
  bricklogger plugins add, and everything else runs — which is what 0.2.0
  promised for an ibos instance after the upgrade. A change written through
  the CLI, the web interface, the API or the MCP server still refuses a type
  that is not installed, so a misspelling is caught where it is typed.
• Running the install script over an installation tells what to restart,
  instead of repeating the guidance for a first install.

Changed

• all, core and status cannot name a plugin type.
• The systemd units are written from templates in the package, by the
  install script and by update alike.

0.2.1 was tagged but never published: its release stopped at a type check
of the tests. 0.2.2 carries everything listed here.