Release v1.0.0

Author: mavam

.plans/woolly-napping-ritchie.md

@@ -0,0 +1,55 @@
+# Plan: Fix uvx fallback for tenzir-node
+
+## Problem
+
+The current uvx fallback for `tenzir-node` runs `uvx tenzir-node`, but `tenzir-node` is not a standalone package—it's a script within the `tenzir` package. The correct command is:
+
+```bash
+uvx --from tenzir tenzir-node
+```
+
+## Solution
+
+Modify `_resolve_binary()` in `src/tenzir_test/config.py` to use `--from tenzir` syntax for `tenzir-node`:
+
+**Current code (line 51-52):**
+
+```python
+if shutil.which("uvx"):
+    return ("uvx", binary_name)
+```
+
+**Updated code:**
+
+```python
+if shutil.which("uvx"):
+    if binary_name == "tenzir-node":
+        return ("uvx", "--from", "tenzir", "tenzir-node")
+    return ("uvx", binary_name)
+```
+
+## Files to Modify
+
+1. **`src/tenzir_test/config.py`** (line 51-52)
+   - Update `_resolve_binary()` to use `--from tenzir` for `tenzir-node`
+
+2. **`tests/test_config.py`** (line 64)
+   - Change expected value from `("uvx", "tenzir-node")` to `("uvx", "--from", "tenzir", "tenzir-node")`
+
+3. **`.docs/src/content/docs/reference/test-framework/index.mdx`** (line 568)
+   - Change `uvx tenzir-node` to `uvx --from tenzir tenzir-node`
+
+4. **`.docs/src/content/docs/guides/testing/write-tests.mdx`** (line 18)
+   - Change `uvx tenzir-node` to `uvx --from tenzir tenzir-node`
+
+## Verification
+
+1. Run unit tests: `uv run pytest tests/test_config.py -v`
+2. Test manually with uvx available but no tenzir-node in PATH
+
+## Commit & Push
+
+After verification, commit and push changes in both repositories:
+
+1. **Main repo** (`$PWD`): Commit code and test changes
+2. **Docs repo** (`$PWD/.docs`): Commit documentation changes

…etect-tenzir-binary-with-uvx-fallback.md …etect-tenzir-binary-with-uvx-fallback.mdchangelog/unreleased/auto-detect-tenzir-binary-with-uvx-fallback.md renamed to changelog/releases/v1.0.0/entries/auto-detect-tenzir-binary-with-uvx-fallback.md changelog/unreleased/auto-detect-tenzir-binary-with-uvx-fallback.md renamed to changelog/releases/v1.0.0/entries/auto-detect-tenzir-binary-with-uvx-fallback.md

@@ -0,0 +1,8 @@
+created: 2026-01-23
+title: Automatic Binary Detection
+intro: >-
+  This release introduces automatic binary detection with a clear precedence order:
+  environment variables take priority, followed by PATH lookup, with `uvx` as fallback.
+  Environment variables now support multi-part commands for full control over binary
+  invocation. The `--tenzir-binary` and `--tenzir-node-binary` CLI flags have been
+  removed in favor of environment variables.

changelog/releases/v1.0.0/manifest.yaml

@@ -0,0 +1,9 @@
+This release introduces automatic binary detection with a clear precedence order: environment variables take priority, followed by PATH lookup, with `uvx` as fallback. Environment variables now support multi-part commands for full control over binary invocation. The `--tenzir-binary` and `--tenzir-node-binary` CLI flags have been removed in favor of environment variables.
+
+## 💥 Breaking changes
+
+### Auto-detect Tenzir binary with uvx fallback
+
+Binary detection now follows a consistent precedence order: environment variable `TENZIR_BINARY` takes priority, followed by a PATH lookup, with `uvx` as the final fallback. The same logic applies to `TENZIR_NODE_BINARY`. Environment variables now support multi-part commands like `TENZIR_BINARY="uvx tenzir"`, giving you full control over how binaries are invoked. The `--tenzir-binary` and `--tenzir-node-binary` CLI flags have been removed in favor of environment variables, which provide more flexibility and clarity.
+
+*By @mavam and @claude in #7.*

changelog/releases/v1.0.0/notes.md

@@ -1,6 +1,6 @@
 [project]
 name = "tenzir-test"
-version = "0.15.0"
+version = "1.0.0"
 description = "Reusable test execution framework extracted from the Tenzir repository."
 readme = "README.md"
 requires-python = ">=3.12"