Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(shorebird_cli): don't fail if a release artifact has already been uploaded #554

Merged
merged 3 commits into from
May 30, 2023

Conversation

bryanoltman
Copy link
Contributor

Description

shorebird release currently fails if it detects that an artifact already exists for a given architecture. This can cause problems if a user's connection is unstable and only some artifact uploads succeed, leaving them in a state where they are unable to complete their release.

This change updates the release artifact upload logic to log when 409s (HttpStatus.conflict) are received instead of aborting the release.

Fixes #553

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@bryanoltman bryanoltman requested review from eseidel and felangel May 26, 2023 17:46
@bryanoltman bryanoltman requested a review from felangel May 30, 2023 15:35
@bryanoltman bryanoltman enabled auto-merge (squash) May 30, 2023 15:37
@bryanoltman bryanoltman merged commit 6abe32b into main May 30, 2023
@bryanoltman bryanoltman deleted the bo/ignore-release-artifact-conflicts branch May 30, 2023 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

chore(shorebird_code_push_client): add detail to error messages when requests fail
2 participants