Merge pull request TangleML#18 from TangleML/piforge/tangle-cli-fix/stable-0-1-0-release-be54bff

chore: prepare 0.1.0 stable release

Author: Volv-G

README.md

@@ -101,7 +101,7 @@ uv run tangle api --help
 uv run tangle sdk pipelines validate pipeline.yaml
 ```
 
-Custom API/codegen users can still run codegen from the fully capable install; generating bindings does not require removing the official `tangle-api` package. For project-local generated APIs, generate into a local source tree such as `src/tangle_api/generated` (and `src/tangle_api/schema/openapi.json` when you want `tangle api --schema-source official`) and run from that project so local `src/tangle_api` shadows site-packages. For packaged custom APIs, publish/provide a distribution named `tangle-api` with a version compatible with this `tangle-cli` release (for example `0.0.1a3+yourorg` for a `tangle-cli` dependency on `tangle-api==0.0.1a3`) via a private index, `--find-links`, or uv sources. As an expert escape hatch, `--no-deps` installs only `tangle-cli` and skips all dependencies, so that environment must manually provide every required runtime dependency plus its generated/custom `tangle_api`; this is acceptable for controlled codegen/custom scenarios but not normal UX.
+Custom API/codegen users can still run codegen from the fully capable install; generating bindings does not require removing the official `tangle-api` package. For project-local generated APIs, generate into a local source tree such as `src/tangle_api/generated` (and `src/tangle_api/schema/openapi.json` when you want `tangle api --schema-source official`) and run from that project so local `src/tangle_api` shadows site-packages. For packaged custom APIs, publish/provide a distribution named `tangle-api` with a version compatible with this `tangle-cli` release (for example `0.1.0+yourorg` for a `tangle-cli` dependency on `tangle-api==0.1.0`) via a private index, `--find-links`, or uv sources. As an expert escape hatch, `--no-deps` installs only `tangle-cli` and skips all dependencies, so that environment must manually provide every required runtime dependency plus its generated/custom `tangle_api`; this is acceptable for controlled codegen/custom scenarios but not normal UX.
 
 ## Agent skills
 
@@ -350,7 +350,7 @@ uv run python -m tangle_cli.openapi.codegen \
   --out src/tangle_api/generated
 ```
 
-That project-local `tangle_api` package can be an editable/package source tree. If you ship the custom API bindings as a wheel or source distribution, use the distribution name `tangle-api` and a compatible version for the `tangle-cli` release you are using. A PEP 440 local version such as `0.0.1a3+yourorg` can satisfy a public `==0.0.1a3` dependency while distinguishing your private build. Provide that package through your private index, `--find-links`, or uv source configuration so the resolver chooses it instead of the public official package.
+That project-local `tangle_api` package can be an editable/package source tree. If you ship the custom API bindings as a wheel or source distribution, use the distribution name `tangle-api` and a compatible version for the `tangle-cli` release you are using. A PEP 440 local version such as `0.1.0+yourorg` can satisfy a public `==0.1.0` dependency while distinguishing your private build. Provide that package through your private index, `--find-links`, or uv source configuration so the resolver chooses it instead of the public official package.
 
 Generate from a backend checkout explicitly:
 

packages/tangle-api/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tangle-api"
-version = "0.0.1a3"
+version = "0.1.0"
 description = "Checked-in generated Tangle API models and operation proxies"
 readme = "README.md"
 authors = [

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tangle-cli"
-version = "0.0.1a3"
+version = "0.1.0"
 description = "CLI for Tangle, the open-source ML pipeline orchestration platform"
 readme = "README.md"
 authors = [
@@ -18,7 +18,7 @@ dependencies = [
     "pydantic>=2.0",
     "pyyaml>=6.0",
     "requests>=2.32.0",
-    "tangle-api==0.0.1a3",
+    "tangle-api==0.1.0",
     "tomli>=2.0; python_version < '3.11'",
 ]
 

tests/test_packaging.py

@@ -179,8 +179,8 @@ def test_tangle_cli_wheel_supports_expert_no_deps_import_path_without_tangle_api
     requires_dist = [line for line in metadata.splitlines() if line.startswith("Requires-Dist: ")]
     assert not any(name.startswith("tangle_api/") for name in names)
     assert "tangle_cli/openapi/openapi.json" not in names
-    assert "Version: 0.0.1a3" in metadata
-    assert "Requires-Dist: tangle-api==0.0.1a3" in requires_dist
+    assert "Version: 0.1.0" in metadata
+    assert "Requires-Dist: tangle-api==0.1.0" in requires_dist
     assert not any("extra == 'native'" in line for line in requires_dist)
     assert "Provides-Extra: native" in metadata
     assert "tangle = tangle_cli.cli:main" in entry_points
@@ -208,7 +208,7 @@ def test_tangle_cli_wheel_supports_expert_no_deps_import_path_without_tangle_api
 
 
 def test_custom_tangle_api_local_version_can_satisfy_cli_pin() -> None:
-    assert Version("0.0.1a3+yourorg") in SpecifierSet("==0.0.1a3")
+    assert Version("0.1.0+yourorg") in SpecifierSet("==0.1.0")
 
 
 def test_tangle_cli_wheel_api_refresh_builds_in_expert_no_deps_fallback(tmp_path) -> None:
@@ -397,7 +397,7 @@ def test_default_wheels_provide_static_client_binding(tmp_path) -> None:
         metadata = archive.read(metadata_name).decode()
 
     requires_dist = [line for line in metadata.splitlines() if line.startswith("Requires-Dist: ")]
-    assert "Version: 0.0.1a3" in metadata
+    assert "Version: 0.1.0" in metadata
     assert "Requires-Dist: pydantic>=2.0" in requires_dist
     assert not any("tangle-cli" in line for line in requires_dist)
     env = {**os.environ, "PYTHONPATH": os.pathsep.join([str(cli_wheel), str(api_wheel)])}