Skip to content

[Snyk] Security upgrade urllib3 from 2.0.7 to 2.6.0 (backport #73) - #74

Open
mergify[bot] wants to merge 1 commit into
edgefrom
mergify/bp/edge/pr-73
Open

[Snyk] Security upgrade urllib3 from 2.0.7 to 2.6.0 (backport #73)#74
mergify[bot] wants to merge 1 commit into
edgefrom
mergify/bp/edge/pr-73

Conversation

@mergify

@mergify mergify Bot commented Jan 5, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • docs/requirements.txt
⚠️ Warning
sphinx 5.3.0 has requirement docutils<0.20,>=0.14, but you have docutils 0.20.1.

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.


This is an automatic backport of pull request #73 done by [Mergify](https://mergify.com).

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-URLLIB3-14192442

(cherry picked from commit f285d38)

# Conflicts:
#	docs/requirements.txt
@mergify mergify Bot added the conflicts label Jan 5, 2026
@mergify
mergify Bot requested a review from skyecas as a code owner January 5, 2026 10:16
@mergify

mergify Bot commented Jan 5, 2026

Copy link
Copy Markdown
Contributor Author

Cherry-pick of f285d38 has failed:

On branch mergify/bp/edge/pr-73
Your branch is up to date with 'origin/edge'.

You are currently cherry-picking commit f285d38.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/requirements.txt

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@mergify mergify Bot added the conflicts label Jan 5, 2026
@skyecas
skyecas force-pushed the mergify/bp/edge/pr-73 branch 2 times, most recently from b0db687 to c6aa38b Compare May 18, 2026 14:21
@skyecas
skyecas force-pushed the mergify/bp/edge/pr-73 branch from c6aa38b to 8cff4ef Compare May 18, 2026 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant