Unpin capybara-mechanize gem on CI #393
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tnir
commented
Jun 16, 2022
by tentatively pinning capybara to 3.36.0 or earlier as capybara 3.37.0 has a breaking change to us: teamcapybara/capybara#2546 Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
tnir
force-pushed
the
tnir-capybara-mechanize-by-pin-capybara-to-3.36
branch
from
0386f0e
to
cd33c49
Compare
This was referenced Jun 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unpin capybara-mechanize gem on CI by tentatively pinning capybara to 3.36.0 or earlier as capybara 3.37.0 has a breaking change to us: teamcapybara/capybara#2546
Replaces #389
Follows up 6a7a17b and #340
Signed-off-by: Takuya Noguchi takninnovationresearch@gmail.com