New version of stripe-rails (1.9.1) broke the build

[depfu]

We've tested your project with an updated dependency and the build failed.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
stripe-rails		1.9.1

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of stripe-rails for this test run.

What changed?

✳️ stripe-rails ( → 1.9.1) · Repo · Changelog

Release Notes

1.9.1

• Fixes issue with rake stripe:verify thanks @Millariel !

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 28 commits:

• prep for release
• Merge pull request #170 from tansengming/feature/webdrivers
• use webdrivers on rails 4 gemfile
• allow chromedriver downloads
• chromedriver-helper -> webdrivers
• Merge pull request #167 from Millariel/master
• oops, now implements suggestion!
• implements suggestion
• Merge branch 'master' into master
• Merge pull request #166 from tansengming/gh-actions-test
• retest
• whitespace
• better ruby version check
• whitespace
• adds CC reporter secret
• adds code climate
• merges build and test
• force bundler version
• use default bundler
• typo
• typo
• adds gemfile matrix
• splits build and test
• removes travis
• pluralizes plans so that rake:verify executes properly
• strategy should be part of jobs
• adds ruby matrix
• initial version of github actions to run test

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)