Skip to content

[0.4] upgrade faraday due to CVE-2026-25765 (#424)#425

Merged
dennis-tismenko merged 1 commit into0.4from
backport/0.4/pr-424
Mar 26, 2026
Merged

[0.4] upgrade faraday due to CVE-2026-25765 (#424)#425
dennis-tismenko merged 1 commit into0.4from
backport/0.4/pr-424

Conversation

@dennis-tismenko
Copy link
Copy Markdown

Backport

This will backport the following commits from main to 0.4:

Questions ?

Please refer to the Backport tool documentation

### elastic/search-team#12889

### Checklists

<!--You can remove unrelated items from checklists below and/or add new
items that may help during the review.-->

#### Pre-Review Checklist
- [ ] This PR does NOT contain credentials of any kind, such as API keys
or username/passwords (double check `crawler.yml.example` and
`elasticsearch.yml.example`)
- [ ] This PR has a meaningful title
- [ ] This PR links to all relevant GitHub issues that it fixes or
partially addresses
- If there is no GitHub issue, please create it. Each PR should have a
link to an issue
- [ ] this PR has a thorough description
- [ ] Covered the changes with automated tests
- [ ] Tested the changes locally
- [ ] Added a label for each target release version (example: `v0.1.0`)
- [ ] Considered corresponding documentation changes
- [ ] Contributed any configuration settings changes to the
configuration reference
- [ ] Ran `make notice` if any dependencies have been added

#### Changes Requiring Extra Attention

<!--Please call out any changes that require special attention from the
reviewers and/or increase the risk to availability or security of the
system after deployment. Remove the ones that don't apply.-->

- [ ] Security-related changes (encryption, TLS, SSRF, etc)
- [ ] New external service dependencies added.

### Related Pull Requests

<!--List any relevant PRs here or remove the section if this is a
standalone PR.

* https://github.com/elastic/.../pull/123-->

### Release Note

<!--If you think this enhancement/fix should be included in the release
notes,
please write a concise user-facing description of the change here.
You should also label the PR with `release_note` so the release notes
author(s) can easily look it up.-->

(cherry picked from commit a9045e1)
@dennis-tismenko dennis-tismenko requested a review from a team as a code owner March 26, 2026 19:20
@dennis-tismenko dennis-tismenko enabled auto-merge (squash) March 26, 2026 19:20
@dennis-tismenko dennis-tismenko merged commit 513b0f7 into 0.4 Mar 26, 2026
2 checks passed
@dennis-tismenko dennis-tismenko deleted the backport/0.4/pr-424 branch March 26, 2026 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants