Bump AIPerf Version

Bump the AIPerf package version everywhere it is hard-coded, then open a PR to main.

The runtime version is read dynamically from package metadata (importlib.metadata.version("aiperf") in src/aiperf/__init__.py), so pyproject.toml is the single source of truth. Every other occurrence is a copy in a doc example or in the mock-server package and must be updated by hand to stay in sync.

Inputs

• Target version (e.g. 0.11.0). If the user did not provide one, read the current version from pyproject.toml and use AskUserQuestion to confirm the target (default: next minor).

Steps

1. Confirm you are starting from an up-to-date main:

   git fetch origin
   git checkout main
   git status

   Only proceed if the working tree is clean (ignore untracked files that are not part of the bump).
2. Find the current version: Read the version field under [project] in pyproject.toml. Call this OLD_VERSION and the requested version NEW_VERSION.
3. Create the branch: Use the <username>/chore-update-version-<NEW_VERSION> convention, e.g.

   git checkout -b harrison/chore-update-version-0.11.0

4. Find every hard-coded occurrence of OLD_VERSION:

   grep -rn --include="*.py" --include="*.toml" --include="*.md" \
     "<OLD_VERSION>" . | grep -v "/.git/"

   Review each hit. Update only strings that mean "the AIPerf version". Do NOT touch unrelated version-like strings (dependency pins, schema_version, sample UUIDs, etc.). uv.lock is deliberately outside this grep: other packages may share the version string, and step 5 regenerates it instead.

   The canonical set of files (as of 0.10.0 -> 0.11.0) is:

   • pyproject.toml — version = "..." under [project]
   • tests/aiperf_mock_server/pyproject.toml — version = "..." under [project]
   • docs/plugins/creating-your-first-plugin.md — the Version: ... line in the pip show example output
   • docs/server-metrics/server-metrics-json-schema.md — every "aiperf_version": "..." JSON example and the (e.g., "...") description (3 occurrences)
   • uv.lock — the root [[package]] name = "aiperf" entry, regenerated by uv lock in step 5 (never hand-edited)

   If the grep surfaces a NEW occurrence not in this list, update it too and add it to this skill's canonical list in the same PR.

5. Regenerate uv.lock:

   uv lock

   uv.lock is tracked and records the root aiperf version, so it must move with pyproject.toml. The PR checks uv sync --locked in run-unit-tests.yml and helm-chart.yml fail on a stale lock, and after merge the nightly's uv lock --check does too. Tests that need the version import aiperf.__version__; leave those alone.
6. Verify nothing stale remains:

   grep -rn "<OLD_VERSION>" pyproject.toml tests/aiperf_mock_server/pyproject.toml \
     docs/plugins/creating-your-first-plugin.md \
     docs/server-metrics/server-metrics-json-schema.md

   This must return no matches. Then confirm NEW_VERSION is present in each, and confirm the lockfile agrees:

   uv lock --check
   git diff uv.lock

   Expect the root aiperf version = line to change. uv lock may also refresh metadata of already-locked packages (for example add an sdist = line published after the lock was generated); that is fine to commit. Investigate if any other package's version = line changes.
7. Run pre-commit on the staged files:

   pre-commit run

   Fix anything it flags before committing.
8. Commit the version bump (commit 1): Stage only the version files explicitly (never git add -A — the working tree may hold unrelated untracked files):

   git add pyproject.toml uv.lock tests/aiperf_mock_server/pyproject.toml \
     docs/plugins/creating-your-first-plugin.md \
     docs/server-metrics/server-metrics-json-schema.md
   git commit -s -F - <<'EOF'
   chore: bump aiperf version to <NEW_VERSION>
   
   Updates the package and mock-server pyproject.toml versions, regenerates
   uv.lock, and refreshes the version strings shown in the plugin tutorial
   example and the server-metrics JSON schema example output.
   
   Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
   EOF

9. Push the branch:

   git push -u origin HEAD

10. Open the PR to main:

    gh pr create \
      --repo ai-dynamo/aiperf \
      --base main \
      --head harrison/chore-update-version-<NEW_VERSION> \
      --title "chore: bump aiperf version to <NEW_VERSION>" \
      --body "$(cat <<'EOF'
    ## Summary
    - Bump AIPerf package version from `<OLD_VERSION>` to `<NEW_VERSION>`.
    - Updates `pyproject.toml`, regenerates `uv.lock`, and updates the mock-server
      `pyproject.toml` and the version strings in the plugin tutorial and
      server-metrics JSON schema docs.
    
    The runtime version is read dynamically from package metadata, so
    `pyproject.toml` is the source of truth; the other files are doc/example copies.
    
    ## Test plan
    - `grep` confirms no `<OLD_VERSION>` strings remain in the bumped files.
    - `uv lock --check` passes.
    - Pre-commit hooks pass.
    EOF
    )"

    If gh is unavailable, print the manual compare URL: https://github.com/ai-dynamo/aiperf/compare/main...harrison/chore-update-version-<NEW_VERSION>
11. Print a summary with the old/new version and the PR link.

Rules

• NEVER manually add a Signed-off-by line — git commit -s adds it.
• NEVER use --no-verify or git commit -n.
• NEVER git add -A / git add .; stage the version files by explicit path so unrelated untracked files stay out of the commit.
• NEVER hand-edit uv.lock (regenerate it with uv lock) or touch non-AIPerf version-like strings.
• Branch from an up-to-date main; one PR = one concern (just the bump).