fix(shorebird_cli): don't fail if a release artifact has already been uploaded #554
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.
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