fix: improve release process robustness and deployment #1990
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
Improves the release process based on issues encountered during v0.1.32 release, making it more robust and adding recovery options.
Changes
Deploy Script (
deploy-local-gateway.sh)--all-instancesflag to deploy to gateway + all 10 peer instances--no-verifyflag for skipping version checksRelease Script (
release.sh)--resume STATE_FILEflag for resuming failed releasesNew Scripts
release-rollback.sh: Complete rollback utility with--yank-cratesoptionRELEASE_RECOVERY.md: Comprehensive manual recovery documentationProblem → Solution
Problem: Deployment failed with "Text file busy" errors
Solution: Disable systemd auto-restart, wait for binary release, then re-enable
Problem: Had to manually deploy to 11 instances one-by-one
Solution:
--all-instancesflag deploys to all at onceProblem: Release script failures left manual cleanup
Solution: State persistence + recovery guide + rollback script
Problem: No version verification after deployment
Solution: Automatic verification with clear error messages
Testing
Tested manually during v0.1.32 release recovery:
Breaking Changes
None. All changes are backward compatible. Existing usage patterns continue to work.
🤖 Generated with Claude Code