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.

Sign up for GitHub

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

Jump to bottom

Temp pin responses==0.23.1 #15513

Merged
merged 2 commits into from
Jul 25, 2023
Merged

Temp pin responses==0.23.1 #15513

merged 2 commits into from
Jul 25, 2023

Conversation

jmsanders
Copy link
Contributor

@jmsanders jmsanders commented Jul 25, 2023 •
edited
Loading

responses==0.23.2 forces us onto urllib>=2.0.0 which causes a whole new pip resolution chain.

getsentry/responses#654

Pinning until all of these packages support urllib3>=2.0.0

@jmsanders
Temp pin responses==0.23.1
5c211c6 
responses==0.23.2 forces us onto urllib>=2.0.0 which causes a whole new
pip resolution chain.

Somehow during that resolution, we end up with very old versions of
boto3 and botocore.

I'm temporarily putting up a pin while I investigate to see if it gets
our builds passing again.
@jmsanders jmsanders requested a review from alangenfeld July 25, 2023 17:54
@jmsanders jmsanders self-assigned this Jul 25, 2023
@jmsanders jmsanders merged commit 2a83082 into master Jul 25, 2023
@jmsanders jmsanders deleted the jordan/temp-pin-responses branch July 25, 2023 20:13
prha pushed a commit that referenced this pull request Jul 25, 2023
@jmsanders @prha
Temp pin responses==0.23.1 (#15513)
2829c2a 
responses==0.23.2 forces us onto urllib>=2.0.0 which causes a whole new
pip resolution chain.

getsentry/responses#654

Pinning until all of these packages support urllib3>=2.0.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alangenfeld alangenfeld alangenfeld approved these changes

Assignees

@jmsanders jmsanders

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@jmsanders @alangenfeld