🚨 [security] [ruby] Update faraday 1.10.3 → 1.10.5 (patch)#2705
Open
depfu[bot] wants to merge 1 commit intodevelopfrom
Open
🚨 [security] [ruby] Update faraday 1.10.3 → 1.10.5 (patch)#2705depfu[bot] wants to merge 1 commit intodevelopfrom
depfu[bot] wants to merge 1 commit intodevelopfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #2705 +/- ##
========================================
Coverage 84.59% 84.59%
========================================
Files 501 501
Lines 20538 20538
Branches 377 377
========================================
Hits 17374 17374
Misses 3161 3161
Partials 3 3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or 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
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
Security Advisories 🚨
🚨 Faraday affected by SSRF via protocol-relative URL host override in build_exclusive_url
Release Notes
1.10.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
Version bump to 1.10.5Update rubocop complexity thresholds for security fixBackport security fix for CVE-2026-25765 to 1.x branch (#1665)Version bump to 1.10.4Make sure that `Faraday::Request::Json` and `Faraday::Response::Json` are correctly autoloaded (#1595)Release Notes
1.0.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 6 commits:
v1.0.1Merge pull request #4 from iox/patch-1CI: Use latest Ruby and bundled gems in PublishCI: Prepare to use latest Ruby in publish workflowPrepare trusted publisherMove documentation from Faraday website to READMERelease Notes
1.2.0
1.1.1
1.1.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
Version bump to 1.2.0Relax `required_ruby_version` to support Ruby 4.0 (#21)CI: Rename Workflows to .yml suffix (#17)v1.1.1Prepare Trusted Publisher (#16)CI: Allow RuboCop to run on Ruby 2.7Unignore .ruby-version fileUse ruby/setup-ruby action in publishVersion bump to 1.1.0Add The Ability To Specify A Different MIME Type (#14)README.md: Use GitHub Actions badge (#13)gemspec: depend on multipart-post ~> 2.0CHANGELOG: correct URLsRelease Notes
1.0.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
v1.0.2Fix conditions for calling `configure_ssl`Commits
See the full diff on Github. The new version differs by 2 commits:
Bump patch version.Modernize gem.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