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

[kantorcodes]

Summary

• sync repository version files to 2.0.958 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.958"

[gemini-code-assist]

Code Review

This pull request updates the version of the hol-guard package from 2.0.922 to 2.0.958 across pyproject.toml, src/codex_plugin_scanner/version.py, and uv.lock. I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• pyproject.toml
• src/codex_plugin_scanner/version.py
• uv.lock

---

_{Reviewed by laguna-m.1-20260312:free · Input: 122K · Output: 1.6K · Cached: 229.7K}

[greptile-apps]

Greptile Summary

This PR syncs the package version metadata after release. The main changes are:

• pyproject.toml version updated to 2.0.958.
• Runtime __version__ updated to 2.0.958.
• Editable package version in uv.lock updated to 2.0.958.

Confidence Score: 5/5

Safe to merge; the changes are limited to repository version metadata.

The modified files consistently update package, runtime, and lockfile version values with no behavioral code changes.

T-Rex Logs

What T-Rex did

• Viewed trex-artifacts/version-sync-01-before.log to verify the initial version state, showing base reports 2.0.922 and all_equal_2.0.958=False.
• Viewed trex-artifacts/version-sync-02-after.log to verify the post-sync state, confirming head reports 2.0.958 consistently and idempotent_diff_exit=0, while the documented sync command still produced an error and sync_repo_version_exit=1.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

1. General comment

   Documented version sync command fails on already-synced 2.0.958 metadata

   • Bug
     • On head 796f08b, pyproject.toml, src/codex_plugin_scanner/version.py, and the editable hol-guard entry in uv.lock all report 2.0.958, and running the command leaves no diff. However, the requested documented command uv sync --frozen && uv run --no-sync python scripts/sync_repo_version.py --version "2.0.958" exits non-zero because the sync script treats an already-correct [project].version line as a failure. This contradicts the claimed idempotence/testing contract.
   • Cause
     • scripts/sync_repo_version.py determines whether a version line was found by checking whether the replacement changed the line. When the line already contains the requested version, _replace_matching_line returns the same line, so _replace_project_version leaves project_version_index unset and raises ValueError, even though the version line exists and is already correct.
   • Fix
     • Track whether the [project].version line matches separately from whether its content changes. Set the found index when the version line pattern matches, write only if the replacement differs, and return (original_text, False) for already-correct metadata. Apply the same idempotence pattern to other version replacement helpers if needed.

   _{Ran code and verified through T-Rex}

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