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

Remove upper bound on boto3 version #542

Merged
merged 1 commit into from
Feb 27, 2018

Conversation

phobologic
Copy link
Member

I can't find a reason for this for limiting us to 1.5 or earlier, and
it's leading to conflicts with other libraries that require newer
versions of botocore.

I can't find a reason for this for limiting us to 1.5 or earlier, and
it's leading to conflicts with other libraries that require newer
versions of botocore.
@codecov-io
Copy link

Codecov Report

Merging #542 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #542   +/-   ##
=======================================
  Coverage   87.57%   87.57%           
=======================================
  Files          95       95           
  Lines        6123     6123           
=======================================
  Hits         5362     5362           
  Misses        761      761

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b39e2a2...137ca20. Read the comment docs.

@russellballestrini russellballestrini merged commit 937f222 into master Feb 27, 2018
@russellballestrini russellballestrini deleted the remove_upper_limit_on_boto3 branch February 27, 2018 16:21
phrohdoh pushed a commit to phrohdoh/stacker that referenced this pull request Dec 18, 2018
…n_boto3

Remove upper bound on boto3 version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants