[Chore] Remove Rye. Fully migrate to UV

[prassanna-ravishankar]

Summary

Complete migration from Rye to UV package management with streamlined development workflow and CI/CD modernization.

Changes

Package Management:

• Migrated from Rye to UV for all dependency management
• Consolidated dev dependencies into [dependency-groups] format
• Removed duplicate lock files (requirements*.lock)

GitHub Workflows:

• Updated all workflows to use setup-uv@v6
• Simplified CI configuration
• Replaced wrapper scripts with direct UV commands
• Removed redundant bin/ directory

Development Workflow:

• Added Taskipy for task management with composition hooks
• Integrated pre-commit configuration
• Cleaned up scripts directory
• Updated documentation (CONTRIBUTING.md, CLAUDE.md)

Key Commands:

• uv run task bootstrap - Setup environment
• uv run task format - Format code and docs (with hooks)
• uv run task lint - Run all checks (with hooks)
• uv run task test - Run tests with mock server

Breaking Changes

Developers need to:

• Install UV instead of Rye
• Use uv run task X instead of ./scripts/X for basic commands
• Run uv run task setup-pre-commit to install hooks

Complex scripts (scripts/test, scripts/mock) preserved unchanged.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	psutil@​7.0.0 ⏵ 6.1.1	+1
	debugpy@​1.8.16 ⏵ 1.8.17	+1
	ddtrace@​3.15.0
	litellm@​1.75.7 ⏵ 1.77.5	+1
	mypy@​1.18.2
	fsspec@​2025.7.0 ⏵ 2025.9.0	+1
	pytest@​8.4.1 ⏵ 8.4.2	+1
	temporalio@​1.15.0 ⏵ 1.18.1	+20		-10
	execnet@​2.1.1
	hf-xet@​1.1.7 ⏵ 1.1.10
	pre-commit@​4.3.0
	distlib@​0.4.0
	identify@​2.6.14
	nox@​2025.5.1
	pyright@​1.1.399
	anyio@​4.10.0 ⏵ 4.11.0	+1
	argcomplete@​3.6.2
	pycparser@​2.22 ⏵ 2.23	+1
	datadog@​0.52.1
	uvicorn@​0.35.0 ⏵ 0.37.0	+1
	mcp@​1.13.0 ⏵ 1.15.0
	jsonschema@​4.25.0 ⏵ 4.25.1	+1
	typer@​0.16.0 ⏵ 0.16.1	+1
	parso@​0.8.4 ⏵ 0.8.5	+1
	legacy-cgi@​2.6.3
	typing-extensions@​4.14.1 ⏵ 4.15.0	+1
	protobuf@​5.29.5 ⏵ 6.32.1	+1
	regex@​2025.7.34 ⏵ 2025.9.18	+1
	pydantic@​2.11.7 ⏵ 2.11.9
	ruff@​0.12.9 ⏵ 0.13.2
	taskipy@​1.14.1
	time-machine@​2.19.0
	pyyaml@​6.0.2 ⏵ 6.0.3
See 24 more rows in the dashboard

View full report

[semgrep-app]

Semgrep identified an issue in your code:
Using variable interpolation ${{...}} with github context data in a run: step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. github context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with env: to store the data and use the environment variable in the run: script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR".

To resolve this comment:

🔧 No guidance has been designated for this issue. Fix according to your organization's approved methods.

💬 Ignore this finding

Reply with Semgrep commands to ignore this finding.

• /fp <comment> for false positive
• /ar <comment> for acceptable risk
• /other <comment> for all other reasons

Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by run-shell-injection.

_{You can view more details about this finding in the Semgrep AppSec Platform.}