Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): add explicit ranges for 'google-api-core' and 'google-auth' #530

Merged
merged 2 commits into from Aug 5, 2021

Conversation

@tseaver
Copy link
Contributor

@tseaver tseaver commented Aug 2, 2021

Transitive dependency resolution breaks unit tests under Python 3.6
following PR #520.

Pin minima for those ranges explicitly when testing under Python 3.6.

Closes #529.

Transitive dependency resolution breaks unit tests under Python 3.6
following PR #520.

Pin minima for those ranges explicitly when testing under Python 3.6.

Closes #529.
@tseaver tseaver requested a review from as a code owner Aug 2, 2021
@google-cla google-cla bot added the cla: yes label Aug 2, 2021
tswast
tswast approved these changes Aug 4, 2021
@gcf-merge-on-green gcf-merge-on-green bot merged commit 310f207 into master Aug 5, 2021
12 checks passed
@gcf-merge-on-green gcf-merge-on-green bot deleted the 529-add-pins-for-api_core-and-auth branch Aug 5, 2021
cojenco added a commit to cojenco/python-storage that referenced this issue Oct 13, 2021
googleapis#530)

Transitive dependency resolution breaks unit tests under Python 3.6
following PR googleapis#520.

Pin minima for those ranges explicitly when testing under Python 3.6.

Closes googleapis#529.
cojenco added a commit to cojenco/python-storage that referenced this issue Oct 13, 2021
googleapis#530)

Transitive dependency resolution breaks unit tests under Python 3.6
following PR googleapis#520.

Pin minima for those ranges explicitly when testing under Python 3.6.

Closes googleapis#529.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

2 participants