Fix(client): update LIBVER to 2.18.2 in google/apiclient #2659
Conversation
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
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Migue98
changed the title
Migue98
changed the title
Migue98
force-pushed
the
fix-libver-version
branch
from
3353085 to
740106f
Compare
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.
Fix: Update
LIBVERto Reflect the Correct VersionThe
LIBVERconstant insrc/Client.phpstill shows"2.12.6"in version2.18.2, which may cause confusion about the actual installed version.This Pull Request updates
LIBVERto"2.18.2"to correctly reflect the installed package version.It might seem like a minor issue, but I spent over an hour trying to figure out why the installed version didn't match the expected one, only to realize it was due to this constant not being updated.
Thanks for reviewing this change!