Release v0.70.0 extends Crush retry behavior so temporary network issues (such as short disconnects or DNS failures) are retried automatically, instead of failing immediately when no specific HTTP error code is returned.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
Adds explicit retry handling for network-layer failures in request execution, reducing manual recovery from transient connectivity issues.
Users of Crush will experience fewer hard failures during brief network hiccups, so prompts and API calls are more likely to succeed without manual reruns or intervention. This is implemented by expanding the retry path from status-code-only conditions to include network exceptions, so operators should monitor for repeated side effects on non-idempotent operations, retry amplification during unstable links, and any increased upstream rate-limit pressure.
Users of Crush will experience fewer hard failures during brief network hiccups, so prompts and API calls are more likely to succeed without manual reruns or intervention. This is implemented by expanding the retry path from status-code-only conditions to include network exceptions, so operators should monitor for repeated side effects on non-idempotent operations, retry amplification during unstable links, and any increased upstream rate-limit pressure.