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

Un-pin capybara gem #2124

Merged
merged 1 commit into from
Jan 24, 2022
Merged

Conversation

jordan-brough
Copy link
Contributor

Several years ago in #1245 capybara was pinned with this message:

Pin the capybara gem, until we can drop Ruby 2.2.0
Any capybara versions above 3.0.0 require a newer Ruby than 2.2.0, which
we will support in line with Rails requirements.

Ruby 2.2 support has been dropped, so I think we can drop the pinning now?

It doesn't really do much at this point anyway since dependabot is automatically
updating to the lastest versions soon after they are released.

Note: Merging this will probably generate some conflicts for #2118, or vice versa.
If one of the PRs gets merged I'll update the other.

Several years ago in PR 1245 this was pinned with this message:

> Pin the capybara gem, until we can drop Ruby 2.2.0
> Any capybara versions above 3.0.0 require a newer Ruby than 2.2.0, which
> we will support in line with Rails requirements.

Ruby 2.2 support has been dropped, so I think we can drop the pinning now?

It doesn't really do much at this point anyway since dependabot is automatically
updating to the lastest versions soon after they are released.
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.

2 participants