What

• Added exponential back-off retry mechanism with full jitter to APIDeploymentsClient
• New constructor params: max_retries, initial_delay, max_delay, backoff_factor
• Migrated build tooling from PDM to uv (hatchling backend)

Why

• Transient server errors (5xx) and rate limits (429) can cause unnecessary failures
• Automatic retries with exponential backoff improve reliability without manual intervention
• Full jitter prevents thundering herd when multiple clients retry simultaneously
• uv is significantly faster than PDM for dependency resolution and installs, and aligns with the broader ecosystem trend

How

• Custom retry logic in _request_with_retry() wrapping all HTTP calls
• Exponential backoff: min(initial_delay * backoff_factor^attempt, max_delay) with full jitter
• Respects Retry-After header for 429 responses
• Async mode (timeout=0) retries POST requests; sync mode skips POST retries to avoid duplicates
• File objects are rewound (seek(0)) before each retry attempt
• Comprehensive test suite with 40+ test cases covering all retry scenarios
• Replaced PDM build backend with hatchling in pyproject.toml
• Replaced pdm.lock with uv.lock
• Updated CI workflow (.github/workflows/main.yml) to use uv instead of PDM
• Updated .pre-commit-config.yaml to use uv-lock hook instead of pdm-lock-check
• Updated .gitignore with uv-specific entries

Can this PR break any existing features. If yes, please list possible items. If no, please explain why.

• No. All retry parameters have sensible defaults matching previous behavior. Setting max_retries=0 disables retries entirely. The PDM→uv migration is a build tooling change only; the published package remains identical.

Database Migrations

• None

Env Config

• None

Relevant Docs

• UN-3230

Related Issues or PRs

• UN-3230

Dependencies Versions

• No new runtime dependencies (uses only stdlib random, time, and existing requests)
• Build tooling: PDM → uv (hatchling backend)

Notes on Testing

• 40+ unit tests in tests/test_retry.py covering: defaults, retryable status codes, delay calculation, connection errors, retry exhaustion, non-retryable codes, Retry-After header, file seek on retry, disabled retry, async vs sync mode behavior
• CI pipeline updated to run with uv

Screenshots

N/A

Checklist

I have read and understood the Contribution Guidelines.