cc298526e9
ci/woodpecker/push/apply Pipeline was successful
Plugin-backed mounts keep their pinned `plugin_version` when a catalog yaml bumps `version`, so the old catalog entry is deregistered while the mount still points at it and the backend fails to start on the next leader change. - add `mount_plugin_version` module tuning `sys/mounts/<path>/tune` to the catalog yaml version for each plugin-backed mount - register new plugin versions before deregistering old ones (`create_before_destroy`) - document the post-bump backend reload in the arrstack plugin yaml - document that a versioned plugin yaml must keep `version` (removing it strands the mount on the old version) Reviewed-on: #171 Co-authored-by: unkin-agent <unkin-agent@unkin.net> Co-committed-by: unkin-agent <unkin-agent@unkin.net>