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

[kantorcodes]

Summary

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

[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!

[greptile-apps]

Greptile Summary

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

• Updates the package version in pyproject.toml.
• Updates the runtime __version__ constant.
• Updates the editable package version in uv.lock.

Confidence Score: 5/5

Safe to merge with minimal risk.

The change only updates matching version metadata across three files. No dependencies, APIs, control flow, or security-sensitive code changed.

No files require special attention.

T-Rex Logs

What T-Rex did

• T-Rex produced a proof for a posted P1 finding and linked it to the corresponding review comment.
• T-Rex validated version-related checks by reviewing the explicit-pr command log, the import check log, the assertion harness log, and the diff log; the explicit-pr command log shows the sync completed but the script exited with code 1, the import check confirms version 2.0.985 with exit code 0, the assertion harness confirms repository metadata assertions passed for 2.0.985 with exit code 0, and the diff log shows no diff for the version files after the script.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
pyproject.toml	Updates the project package version from 2.0.967 to 2.0.985.
src/codex_plugin_scanner/version.py	Updates the exported scanner __version__ to 2.0.985.
uv.lock	Updates the editable hol-guard package entry to version 2.0.985.

Comments Outside Diff (1)

1. General comment

   Explicit version sync CLI fails even when metadata is already aligned

   • Bug
     • The PR's stated validation command fails when run exactly: /opt/greptile/trusted-bin/uv sync --frozen && /opt/greptile/trusted-bin/uv run --no-sync python scripts/sync_repo_version.py --version "2.0.985". The script reports Error: Could not update [project].version in /home/user/repo/pyproject.toml. Follow-up checks confirm the visible metadata is already synchronized to 2.0.985, so this appears to be a release-script/test-plan failure rather than a version-value mismatch.
   • Cause
     • The CLI path in scripts/sync_repo_version.py cannot update or recognize the existing [project].version entry in pyproject.toml under the current repository state, and exits non-zero instead of succeeding idempotently when the target version is already present.
   • Fix
     • Update scripts/sync_repo_version.py so the CLI can handle the current pyproject.toml format and is idempotent when [project].version already equals the requested version. Then rerun the exact PR validation command.

   _{Ran code and verified through T-Rex}

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

[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: 110.4K · Output: 3K · Cached: 390.9K}