v0.1.35 - Release 0.1.35 with rate-rejected JSON request retries (#61)

🌟 Summary

ultralytics-platform SDK 0.1.35 improves reliability for long-running workflows by retrying rate-limited JSON API requests instead of failing immediately. 🚀

📊 Key Changes

• 🔁 Added HTTP 429 Too Many Requests retries for requests with JSON bodies in both:
  • Synchronous clients
  • Asynchronous clients
• ⏳ Preserved existing retry limits and Retry-After behavior, so clients continue to respect server-provided timing guidance.
• 🧩 Updated the shared generated client while keeping the API contract unchanged.
• 🛡️ Avoided introducing retries for potentially unsafe cases, including:
  • Ambiguous mutation failures
  • Requests with non-JSON bodies
  • Existing POST 500 scenarios that could unintentionally replay a request
• 📦 Bumped the SDK version from 0.1.34 to 0.1.35.
• ✅ Verified through formatting, linting, package builds, byte compilation, consumer tests, and real HTTP-server retry checks.

🎯 Purpose & Impact

• 🌐 Long-running Ultralytics Platform workflows—such as those affected by dataset adoption rate limits—can now continue automatically after temporary rate limiting.
• 💪 Improves resilience for both synchronous and asynchronous applications without requiring user code changes.
• 🔒 Maintains safer retry behavior by limiting the fix to retryable JSON requests and preserving existing protections against replaying uncertain operations.
• 🔄 Because the API contract is unchanged, upgrading to 0.1.35 should be straightforward for existing SDK users.

What's Changed

• Release 0.1.35 with JSON rate-limit retries by @glenn-jocher in #61

Full Changelog: v0.1.34...v0.1.35