Update ConfirmingClient to use API version 1_9 #25
Conversation
This file contains 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
No schema changes were made to the API between version 1_7 and 1_9.
3 tasks
|
I've been thinking about a lazy way to handle this. I can't really be expected to monitor the API versions and constantly update the library. Perhaps it could somehow be automated to an extent, but in theory it really needs testing to know it still works. I wonder why the API versions increase so often, especially when there doesn't appear to be a backward compatibility breaking change... it's a stupid release policy for an API I must say. |
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.
No schema changes were made to the API between version 1_7 and 1_9 (documentation), so no actual changes to our code are needed.