fix(release): bump crates.io verify polling 12→30 attempts (3min→7.5min)#37
Merged
Merged
Conversation
v0.1.0 needed >30s for crates.io API propagation after `cargo publish` returned. v0.2.0 (workflow run 25604826136 on tag push 2026-05-09 15:31Z) hit the same race at the longer end — `cargo publish` succeeded at 15:34:21Z, the version row was immediately created in the crates.io DB (visible via `created_at` on the version metadata when queried 30s after the verify-step's final attempt), but the public API endpoint served a cached 404 for the entire 3-minute polling window. Workflow red-flagged a successful publish. Bump to 30 × 15s = 7.5min covers the observed envelope with headroom. The polling-instead-of-sleeping pattern means the workflow still exits quickly when propagation is fast (typical case: 30-60s). Verified locally that the new polling logic returns success on first attempt against the live v0.2.0 entry. Signed-off-by: Saurabh Jain <dev@getaxonflow.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The `Verify version is live on crates.io` step in release.yml false-failed during the v0.2.0 release (workflow run 25604826136). `cargo publish` succeeded; the version was created in the crates.io DB at 15:34:21Z (verified via `created_at` field on `/api/v1/crates/axonflow-sdk-rust/0.2.0` checked manually 30 seconds after the polling window closed), but the public API endpoint served a cached 404 for the entire 3-minute polling window (15:34:23Z → 15:37:24Z).
Change
Bump the polling loop from `12 × 15s = 3min` to `30 × 15s = 7.5min`. Polling-instead-of-sleeping preserves the fast-exit on typical fast-propagation cases (30-60s).
DoD (dryrun)
Ran the new polling logic locally against the live v0.2.0 entry — returns success on first attempt:
```
$ for i in $(seq 1 30); do
if curl -sf "https://crates.io/api/v1/crates/axonflow-sdk-rust/0.2.0" > /dev/null; then
echo "✅ axonflow-sdk-rust@0.2.0 is live on crates.io (after ${i} attempt(s))"
break
fi
sleep 15
done
✅ axonflow-sdk-rust@0.2.0 is live on crates.io (after 1 attempt(s))
```
Self-review
CHANGELOG.md / Cargo.toml / source code unchanged.