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
faraday
~> 0.9
0.17.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 faraday for this test run.
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)
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.
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 faraday for this test run.
What changed?
✳️ faraday (~> 0.9 → 0.17.1) · Repo · Changelog
Release Notes
0.17.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 38 commits:
add release notes for Faraday v0.17.1 (#1082)
Merge pull request #1081 from lostisland/0.1x-ruby-2.7-fixes
This fixes warnings on Ruby 2.7 (#1009)
Merge pull request #1076 from lostisland/0.1x-deprecate-fixes-2
Merge pull request #1077 from BobbyMcWho/deprecate-changes
Remove the intermediate variable
teach DeprecatedClass.proxy_class to accept a different ver
remove usage of ===
Merge pull request #1066 from lostisland/0.1x-changelog
update authors
clean up that copy pasta
update homepage, add changelog/source code/bug tracker urls, and include changelog and tests with gem file.
Add release notes from v0.9.2 - v0.17.0 to the Changelog
Merge pull request #1064 from lostisland/0.1x-nil-error
remove references to deprecated error classes
introduce NilStatusError to the RaiseError middleware
Merge pull request #1059 from lostisland/0.1x-deprecate-fix
use rspec expect syntax to test the error handling
remove unnecessary #tap
Update lib/faraday/deprecate.rb
squelch this
Merge pull request #1058 from lostisland/0.1x-spec
allow deprecated exception classes to rescue the current exception class
Teach proxy_class how to work with root-level superclasses
rspec junit formatter is unused
randomize spec order and disable monkey patching
ignore docs dir on 0.1x
Run rspec alongside test/unit
Merge pull request #1054 from BobbyMcWho/create-faraday-deprecation-class
Merge branch '0.1x' into create-faraday-deprecation-class
Merge pull request #1055 from lostisland/0.1x-ci-update
where we're going... we don't need... linting...
update ci workflow in this branch only
bring them back
remove GH Actions config since it's only read from master
replace travis config with gh actions
Rescue correct error
Create Faraday Deprecate class.
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