Replicate Skipped v1.0.5 Because Their Release System Broke — Here's a Reliable Alternative

Replicate's own release notes for Python SDK v1.0.6 contain a quiet admission that should concern any developer building production AI pipelines: "the release system failed and we chose not to re-use the identifier" Version 1.0.5 simply doesn't exist. Their automated CI/CD pipeline broke during a routine version bump, so they skipped it entirely. This is a small thing. But small things reveal big patterns. Why This Matters for Your AI Pipeline SDK release pipelines are foundational infrastructure. When a company's own tooling breaks on a simple version increment, it raises legitimate questions: If their release CI/CD breaks, what else breaks silently? What happens to your predictions during an infrastructure incident? How much engineering bandwidth is going to internal tooling vs. developer experience? Replicate is a solid product with a large model library. But the SDK has had a pattern of issues: v1.0.1 : Timeout errors on long-running predictions (developers had to pin to 0.34.1) v1