fix: make release publishing resilient to restarts #386

Merged

navicore-bot merged 3 commits from fix/release-publish-resilience into main

2026-03-30 00:33:33 +00:00

navicore-bot commented

2026-03-29 22:02:54 +00:00

(Migrated from github.com)

Summary

Add --no-verify to all cargo publish commands since tests already run in an earlier step
Increase sleep between crate publishes from 60s to 120s to allow crates.io indexing to complete (indexing can take 2-5 minutes)
Add || echo fallback to publish commands so already-published crates don't fail the workflow on restart

Fixes #384

Test plan

Verify the workflow YAML is valid
Trigger a release and confirm crates publish successfully
Restart a release to confirm already-published crates are handled gracefully

🤖 Generated with Claude Code

## Summary - Add `--no-verify` to all `cargo publish` commands since tests already run in an earlier step - Increase sleep between crate publishes from 60s to 120s to allow crates.io indexing to complete (indexing can take 2-5 minutes) - Add `|| echo` fallback to publish commands so already-published crates don't fail the workflow on restart Fixes #384 ## Test plan - [ ] Verify the workflow YAML is valid - [ ] Trigger a release and confirm crates publish successfully - [ ] Restart a release to confirm already-published crates are handled gracefully 🤖 Generated with [Claude Code](https://claude.com/claude-code)

navicore commented

2026-03-29 23:12:45 +00:00

(Migrated from github.com)

@navicore-bot please run "just fmt" to fix fmt errors and run "just ci" to make sure tests pass (they are not passing in gha).