Skip to content

Conversation

@sestinj
Copy link
Contributor

@sestinj sestinj commented Oct 31, 2025

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):

  • manual-testing-sandbox/requirements.txt
⚠️ Warning
typer 0.3.2 has requirement click<7.2.0,>=7.1.1, but you have click 8.1.8.
thinc 8.0.17 requires murmurhash, which is not installed.
thinc 8.0.17 requires preshed, which is not installed.
thinc 8.0.17 requires cymem, which is not installed.
spacy 3.1.2 requires preshed, which is not installed.
spacy 3.1.2 requires murmurhash, which is not installed.
spacy 3.1.2 requires cymem, which is not installed.
qtconsole 5.4.4 requires pyzmq, which is not installed.
notebook 6.5.7 requires pyzmq, which is not installed.
jupyter-server 1.24.0 requires pyzmq, which is not installed.
jupyter-console 6.6.3 requires pyzmq, which is not installed.
jupyter-client 7.4.9 requires pyzmq, which is not installed.
ipykernel 6.16.2 requires pyzmq, which is not installed.
exceptiongroup 1.3.0 has requirement typing-extensions>=4.6.0; python_version < "3.13", but you have typing-extensions 3.10.0.2.

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:

🦉 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.

  • Migration
    • Keras 3 requires a backend. Ensure TensorFlow, PyTorch, or JAX is installed; the sandbox already pins torch==2.6.0.
    • Set KERAS_BACKEND (e.g., "torch") if needed and run tests; update any Keras 2.x-specific APIs.

Written for commit 7bf4463. Summary will update automatically on new commits.

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-KERAS-13743411
@sestinj sestinj requested a review from a team as a code owner October 31, 2025 08:45
@sestinj sestinj requested review from tingwai and removed request for a team October 31, 2025 08:45
@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Oct 31, 2025
@github-actions
Copy link

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

  • feat: add changelog generation support
  • fix: resolve login redirect issue
  • docs: update README with new instructions
  • chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

  • 📝 Automatic changelog generation
  • 🚀 Automated semantic versioning
  • 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

@github-actions
Copy link


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


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.

@github-actions
Copy link

github-actions bot commented Oct 31, 2025

✅ Review Complete

Code Review Summary

⚠️ Continue API authentication failed. Please check your CONTINUE_API_KEY.


Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a 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
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot Oct 31, 2025

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>
Fix with Cubic

@RomneyDa
Copy link
Collaborator

RomneyDa commented Nov 3, 2025

manual testing sandbox doesn't matter

@RomneyDa RomneyDa closed this Nov 3, 2025
@github-project-automation github-project-automation bot moved this from Todo to Done in Issues and PRs Nov 3, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Nov 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants