fix: Include discovery artifacts in published package - #1221
Merged
gcf-merge-on-green[bot] merged 1 commit intoMar 4, 2021
Merged
fix: Include discovery artifacts in published package#1221gcf-merge-on-green[bot] merged 1 commit into
gcf-merge-on-green[bot] merged 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
busunkim96
approved these changes
Mar 4, 2021
Copy link
Copy Markdown
Contributor
|
Confirmed that the fix works for me locally. Thanks @parthea! |
Sorry, something went wrong.
gcf-merge-on-green
Bot
deleted the
fix-missing-documents-in-published-version
branch
March 4, 2021 17:02
gcf-merge-on-green Bot
pushed a commit
that referenced
this pull request
Mar 4, 2021
🤖 I have created a release \*beep\* \*boop\* --- ### [2.0.2](https://www.github.com/googleapis/google-api-python-client/compare/v2.0.1...v2.0.2) (2021-03-04) ### Bug Fixes * Include discovery artifacts in published package ([#1221](https://www.github.com/googleapis/google-api-python-client/issues/1221)) ([ad618d0](https://www.github.com/googleapis/google-api-python-client/commit/ad618d0b266b86a795871d946367552905f4ccb6)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This was referenced Mar 8, 2021
4 tasks
parthea
added a commit
that referenced
this pull request
Apr 20, 2021
gcf-merge-on-green Bot
pushed a commit
that referenced
this pull request
Apr 20, 2021
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly: - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/google-api-python-client/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) Fixes #1235 🦕 In an attempt to verify that this is a fix for #1235 I'm going push a commit that removes the fix from #1221 in this PR and confirm that the checks fail.
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
Reviewers
1 more reviewer2 participants
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.
Fixes #1214 🦕
I was able to re-create the issue by using the following steps.
To Verify the fix, repeat the steps above, but apply the update in this PR prior to installing the library.