Open
Conversation
|
Kudos, SonarCloud Quality Gate passed!
|
|
Just FYI: our API integration was broken since Friday and today got escalated to interrupt my vacation! :-D |
|
Just for the record and users searching for a solution...
I also got an email from GoShippo Support suggesting this solution. |
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.








The Shippo API server apparently now requires an API version to be provided, but the Ruby gem doesn't include a default version. Users can get around this by setting it themselves, e.g.:
The gem is obviously built to interact using a particular version of the API, and this PR makes that version explicit.