chore(release): sync repository version to 2.0.972 [skip release publish]

[kantorcodes]

Summary

• sync repository version files to 2.0.972 after publish
• keep repo-visible version metadata aligned with the released package artifacts

Testing

• uv sync --frozen && uv run --no-sync python scripts/sync_repo_version.py --version "2.0.972"

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• pyproject.toml - version string update (2.0.967 → 2.0.972)
• src/codex_plugin_scanner/version.py - version string update (2.0.967 → 2.0.972)
• uv.lock - version string update (2.0.967 → 2.0.972)

---

_{Reviewed by laguna-m.1-20260312:free · Input: 138.9K · Output: 2.4K · Cached: 210.3K}

[greptile-apps]

Greptile Summary

This PR syncs the repository version metadata to 2.0.972. The main changes are:

• pyproject.toml project version updated from 2.0.967 to 2.0.972.
• src/codex_plugin_scanner/version.py runtime __version__ updated to 2.0.972.
• uv.lock editable package entry updated to 2.0.972.

Confidence Score: 5/5

Safe to merge with minimal risk.

Changes are limited to consistent version metadata updates across three files. No logic, dependency, API, schema, or security-sensitive changes were introduced.

No files require special attention.

T-Rex Logs

What T-Rex did

• Compared the baseline state with the post-sync state and confirmed the versions advanced from 2.0.967 to 2.0.972 with all_aligned still true.
• Recorded the documented head-sync steps showing uv sync --frozen succeeded and hol-guard==2.0.972 was installed.
• Observed that syncing the repository version via sync_repo_version.py --version "2.0.972" failed with exit code 1.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
pyproject.toml	Project package metadata version was updated from 2.0.967 to 2.0.972 with no functional code changes.
src/codex_plugin_scanner/version.py	Runtime __version__ constant was updated to match the released package version.
uv.lock	Editable root package entry in the lockfile was updated to 2.0.972; dependencies remain unchanged.

Comments Outside Diff (1)

1. General comment

   Documented version sync command fails on already-synced 2.0.972 head

   • Bug
     • The release-sync metadata files are aligned at 2.0.972 on head, but the documented reproduction command fails when run against that already-synced head worktree. The script reports Error: Could not update [project].version in /tmp/trex-version-sync/head/pyproject.toml and exits 1, contradicting the claim that this command can reproduce/sync the repository version state after publish.
   • Cause
     • scripts/sync_repo_version.py treats an unchanged replacement as if no [project].version line was found. In _replace_project_version, project_version_index is only set when replaced_line != line; when the requested version is already present, _replace_matching_line returns the original line, leaving project_version_index as None and raising at the raise ValueError(f"Could not update [project].version in {path}") path. The same idempotency pattern may affect the module version replacement as well.
   • Fix
     • Make the replacement helpers detect a matching version line independently from whether the text changes. For example, set the found index whenever the version-line regex matches, assign the replacement result, and return updated_text != text; do not raise merely because the requested version was already present.

   _{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore(release): sync repository version ..." | Re-trigger Greptile}