fruxon 0.9.2__tar.gz → 0.9.3__tar.gz

{fruxon-0.9.2 → fruxon-0.9.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fruxon
-Version: 0.9.2
+Version: 0.9.3
 Summary: The Fruxon SDK is a lightweight Python client for integrating with the Fruxon platform.
 Project-URL: bugs, https://github.com/fruxon-ai/fruxon-sdk/issues
 Project-URL: changelog, https://github.com/fruxon-ai/fruxon-sdk/blob/main/HISTORY.md

{fruxon-0.9.2 → fruxon-0.9.3}/src/fruxon/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '0.9.2'
-__version_tuple__ = version_tuple = (0, 9, 2)
+__version__ = version = '0.9.3'
+__version_tuple__ = version_tuple = (0, 9, 3)
 
 __commit_id__ = commit_id = None

{fruxon-0.9.2 → fruxon-0.9.3}/tests/conftest.py

@@ -59,6 +59,14 @@ def _scrub_cli_env(monkeypatch: pytest.MonkeyPatch, tmp_path_factory: pytest.Tem
 
     for var in _SCRUB_ENV:
         monkeypatch.delenv(var, raising=False)
+    # Hard-disable telemetry for the whole suite. Without this, any test
+    # that drives a real CLI command flow (e.g. the doctor tests, which
+    # set FRUXON_TOKEN=fx_pat_x) spins up the background telemetry thread
+    # and POSTs to the *production* ingest endpoint — leaking bogus events
+    # under a fake token and tripping its rate limiter. Tests that assert
+    # telemetry's own on/off resolution clear this var in their local
+    # fixture (and mock the network), so they're unaffected.
+    monkeypatch.setenv("FRUXON_NO_TELEMETRY", "1")
     monkeypatch.setenv("FRUXON_NO_KEYRING", "1")
     config_dir = tmp_path_factory.mktemp("fruxon-config")
     monkeypatch.setenv("FRUXON_CONFIG_DIR", str(config_dir))