-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Snyk] Security upgrade keras from 2.6.0 to 3.12.0 #8536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The following vulnerabilities are fixed by pinning transitive dependencies: - https://snyk.io/vuln/SNYK-PYTHON-KERAS-13743411
|
|
I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
|
✅ Review Complete Code Review Summary |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 issue found across 1 file
Prompt for AI agents (all 1 issues)
Understand the root cause of the following 1 issues and fix them.
<file name="manual-testing-sandbox/requirements.txt">
<violation number="1" location="manual-testing-sandbox/requirements.txt:29">
Upgrading keras to 3.12.0 conflicts with the existing tensorflow==2.6.0 pin, which depends on keras~=2.6.0. This will make the requirements set unsatisfiable until TensorFlow is upgraded in tandem.</violation>
</file>
React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.
| # Deep Learning | ||
| torch==2.6.0 | ||
| keras==2.6.0 | ||
| keras==3.12.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upgrading keras to 3.12.0 conflicts with the existing tensorflow==2.6.0 pin, which depends on keras~=2.6.0. This will make the requirements set unsatisfiable until TensorFlow is upgraded in tandem.
Prompt for AI agents
Address the following comment on manual-testing-sandbox/requirements.txt at line 29:
<comment>Upgrading keras to 3.12.0 conflicts with the existing tensorflow==2.6.0 pin, which depends on keras~=2.6.0. This will make the requirements set unsatisfiable until TensorFlow is upgraded in tandem.</comment>
<file context>
@@ -26,7 +26,7 @@ spacy==3.1.2
# Deep Learning
torch==2.6.0
-keras==2.6.0
+keras==3.12.0
# Image processing
</file context>
|
manual testing sandbox doesn't matter |
Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.
Snyk changed the following file(s):
manual-testing-sandbox/requirements.txtImportant
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:
🦉 Deserialization of Untrusted Data
Summary by cubic
Upgraded Keras from 2.6.0 to 3.12.0 in manual-testing-sandbox/requirements.txt to fix vulnerability SNYK-PYTHON-KERAS-13743411. Improves security and aligns the sandbox with Keras 3.
Written for commit 7bf4463. Summary will update automatically on new commits.