Skip to content

Remove < 2.0 Faraday version restriction#1415

Merged
orta merged 7 commits into
danger:masterfrom
vilmantas:master
Jan 28, 2023
Merged

Remove < 2.0 Faraday version restriction#1415
orta merged 7 commits into
danger:masterfrom
vilmantas:master

Conversation

@vilmantas

@vilmantas vilmantas commented Jan 16, 2023

Copy link
Copy Markdown
Contributor

Updating to allow Faraday 2.0.0.

Locking between versions of ">= 0.9.0", "< 2.0" was causing new projects to have dependency conflicts.

Related: #1349

@vilmantas vilmantas changed the title Bump faraday version to 2.0.0 Remove > 2.0 Faraday version restriction Jan 16, 2023
@vilmantas vilmantas changed the title Remove > 2.0 Faraday version restriction Remove < 2.0 Faraday version restriction Jan 16, 2023
@vilmantas vilmantas mentioned this pull request Jan 18, 2023
@orta

orta commented Jan 18, 2023

Copy link
Copy Markdown
Member

You've got CI running properly now, looks like its got some failing tests in the gitlab side

@vilmantas

Copy link
Copy Markdown
Contributor Author

@orta

not sure if I understand the errors. Are the other gems broken due to this change?

@orta

orta commented Jan 19, 2023

Copy link
Copy Markdown
Member

I dont know much about web mock - but maybe it also uses faraday and by allowing for the pdated faraday it breaks webmock?

@oleg-vinted oleg-vinted left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As for the test failures, they also happen in current master when using Ruby 3.2. So they seem to be caused by #1411.

Comment thread danger.gemspec Outdated
spec.add_runtime_dependency "colored2", "~> 3.1"
spec.add_runtime_dependency "cork", "~> 0.1"
spec.add_runtime_dependency "faraday", ">= 0.9.0", "< 2.0"
spec.add_runtime_dependency "faraday", ">= 0.9.0", "~> 2.0.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This version constraint doesn't make much sense as the second part makes the first one redundant. You probably want ">= 0.9.0", "< 3.0"

@orta

orta commented Jan 28, 2023

Copy link
Copy Markdown
Member

Thanks folks - I dropped 3.2 from CI, so this should be fine I think

@orta orta merged commit dbc311f into danger:master Jan 28, 2023
@orta

orta commented Jan 28, 2023

Copy link
Copy Markdown
Member

Shipped as 9.2.0

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.

3 participants