build: set release test version to 0.0.1

Author: nachiketb-nvidia

.agents/skills/publish-package/SKILL.md

@@ -12,7 +12,7 @@ wheels separate from official tag-gated release builds.
 |---|---|---|---|---|
 | Dev wheel artifact | Manual `publish.yml` dispatch with `build_dev_artifact=true` | GitHub Actions | One-day GitHub artifact | `docs/internal/dev_wheel_artifacts.md` |
 | Dev matrix artifact | Manual `publish.yml` dispatch with `build_dev_matrix=true` | GitHub Actions | Full matrix GitHub artifacts | `docs/internal/dev_wheel_artifacts.md` |
-| Official release build | Root `v0.1.0`-style tag | GitHub Actions `.github/workflows/publish.yml` | Full release artifact matrix + PyPI Trusted Publishing via `uv publish` | `.github/workflows/publish.yml` |
+| Official release build | Root `vMAJOR.MINOR.PATCH` tag | GitHub Actions `.github/workflows/publish.yml` | Full release artifact matrix + PyPI Trusted Publishing via `uv publish` | `.github/workflows/publish.yml` |
 
 GitHub-hosted runners cannot currently reach NVIDIA-internal Artifactory or Kitmaker Portal from
 this repo, and GitHub Packages is not a PyPI-compatible package index. Do not add Artifactory,
@@ -26,7 +26,7 @@ changes and the release process is explicitly approved.
 - Do not publish dev wheels to PyPI from manual workflow dispatch.
 - Keep `.dev` artifacts public-safe because GitHub Actions artifacts may be shared for review.
 - Full wheel matrices may run manually for validation, but PyPI publishing belongs only on root
-  `v0.1.0`-style tag releases.
+  `vMAJOR.MINOR.PATCH` tag releases.
 - Manual dev builds should build exactly one Linux x86_64 wheel artifact with one-day retention.
 - Use PyPI Trusted Publishing with the GitHub environment named `pypi`; do not add long-lived PyPI tokens.
 

.github/workflows/publish.yml

@@ -31,8 +31,8 @@ permissions:
 
 jobs:
   # OSS-style split:
-  # - Root v0.1.0-style tags run validation, build the complete matrix, publish to PyPI, and create a
-  #   GitHub Release.
+  # - Root vMAJOR.MINOR.PATCH tags run validation, build the complete matrix, publish to
+  #   PyPI, and create a GitHub Release.
   # - Manual dev builds create artifacts only. They are useful for branch validation but never
   #   publish to PyPI.
   #
@@ -57,7 +57,7 @@ jobs:
 
           tag = os.environ["GITHUB_REF_NAME"]
           if not re.fullmatch(r"v\d+\.\d+\.\d+", tag):
-              raise SystemExit(f"release tags must look like v0.1.0, got {tag!r}")
+              raise SystemExit(f"release tags must look like vMAJOR.MINOR.PATCH, got {tag!r}")
 
           with open("pyproject.toml", "rb") as file:
               pyproject = tomllib.load(file)

docs/internal/dev_wheel_artifacts.md

@@ -7,8 +7,8 @@ Switchyard currently follows the OSS-style NeMo path for GitHub builds:
 - regular CI runs tests, linting, type checks, Rust checks, and slim-install smoke checks;
 - manual dev builds create one Linux x86_64 wheel as a one-day GitHub Actions artifact;
 - manual dev matrix builds create the full sdist and wheel set as GitHub Actions artifacts;
-- root `v0.1.0`-style tags run the complete release validation and wheel matrix;
-- public PyPI/GitHub publishing happens only from approved `v0.1.0`-style tag releases.
+- root `vMAJOR.MINOR.PATCH` tags run the complete release validation and wheel matrix;
+- public PyPI/GitHub publishing happens only from approved `vMAJOR.MINOR.PATCH` tag releases.
 
 Wheel metadata uses the public distribution name `nemo-switchyard`, while the Python import and CLI
 stay `switchyard`.
@@ -61,7 +61,7 @@ publish anything to PyPI.
 
 ## Official Release Build
 
-Create a root `v0.1.0`-style tag only when a real release has been approved. Tag pushes run:
+Create a root `vMAJOR.MINOR.PATCH` tag only when a real release has been approved. Tag pushes run:
 
 - Python release checks on Python 3.12, 3.13, and 3.14;
 - Rust fmt, clippy, and workspace tests;
@@ -71,7 +71,7 @@ Create a root `v0.1.0`-style tag only when a real release has been approved. Tag
 - native wheel smoke installs where the runner can execute the artifact.
 
 The workflow rejects release tags that do not exactly match `pyproject.toml`'s package version. For
-the `0.1.0` release, push the `v0.1.0` tag.
+example, package version `0.0.1` must be released with the `v0.0.1` tag.
 
 The official `publish` job uses `uv publish --trusted-publishing always`, so PyPI project creation
 and uploads require a matching pending trusted publisher:

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "maturin"
 
 [project]
 name = "nemo-switchyard"
-version = "0.1.0"
+version = "0.0.1"
 description = "Typed, composable LLM routing with request/response translation and multi-backend orchestration"
 readme = "README.md"
 license = "Apache-2.0"

switchyard/__init__.py

@@ -240,4 +240,4 @@ def __getattr__(name: str) -> Any:
     "AnyResponseStream",
 ]
 
-__version__ = "0.1.0"
+__version__ = "0.0.1"