fix(ci): use --frozen flag to prevent uv.lock drift in CI

[PythonFZ]

Prevents uv sync from modifying uv.lock during CI runs, which caused the benchmark action to fail when switching to gh-pages branch.

Summary by CodeRabbit

• Chores
  • Updated CI/CD workflows to enforce frozen dependency versions, ensuring consistent and reproducible builds across all test and benchmark environments.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ccbaabcd-9386-4ab5-a6f7-b2ff0729e06d

📥 Commits

Reviewing files that changed from the base of the PR and between 765174a and 76eea81.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• .github/workflows/benchmark.yml
• .github/workflows/tests.yml

---

📝 Walkthrough

Walkthrough

GitHub Actions workflow files are modified to enforce frozen dependency states during package synchronization by adding the --frozen flag to uv sync commands in both benchmark and test workflows.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflows .github/workflows/benchmark.yml, .github/workflows/tests.yml	Added --frozen flag to uv sync command to enforce frozen dependency state during synchronization, ensuring exact dependency versions are locked.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Dependencies frozen, locked in place,
No surprises in this workflow's space,
Two little flags, so precise and true,
Now uv knows exactly what to do! ❄️

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/benchmark-lock

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}