Back to development: 0.1.4+dev

A tag is the only thing that is a version. Between two of them the tree is a
build nobody released, and until now it went on claiming to *be* the release
it came after — which is how 0.1.4 came to name both the build before the
per-node digest and the build after, with the mismatch messages unable to tell
them apart.

`+dev` is a local version: it says "0.1.4, plus changes", it does not have to
guess what the next release will be numbered, and PyPI refuses one, so a dev
build cannot be published by accident. `scripts/release.sh` in the workspace
root writes it after each tag; this is that commit, by hand, for the release
that predates it.

backend/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "fluksio"
-version = "0.1.4"
+version = "0.1.4+dev"
 description = "Node-based automation engine: flows, dashboards, batch runs"
 readme = "README.md"
 license = "AGPL-3.0-or-later"

uv.lock

@@ -869,7 +869,7 @@ wheels = [
 
 [[package]]
 name = "fluksio"
-version = "0.1.4"
+version = "0.1.4+dev"
 source = { editable = "backend" }
 dependencies = [
     { name = "aiomqtt" },
@@ -955,7 +955,7 @@ dev = [
 
 [[package]]
 name = "fluksio-worker"
-version = "0.1.4"
+version = "0.1.4+dev"
 source = { editable = "worker" }
 dependencies = [
     { name = "websockets" },

worker/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "fluksio-worker"
-version = "0.1.4"
+version = "0.1.4+dev"
 description = "Runs Fluksio nodes on a machine the engine cannot reach"
 readme = "README.md"
 license = "AGPL-3.0-or-later"