Skip to content

[Snyk] Security upgrade jupyter-server from 1.24.0 to 2.18.2 - #25

Open
anaconda-security-bot wants to merge 1 commit into
masterfrom
snyk-fix-748cef211ffb8bd90db91122eeea8608
Open

[Snyk] Security upgrade jupyter-server from 1.24.0 to 2.18.2#25
anaconda-security-bot wants to merge 1 commit into
masterfrom
snyk-fix-748cef211ffb8bd90db91122eeea8608

Conversation

@anaconda-security-bot

Copy link
Copy Markdown

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

  • requirements.txt
⚠️ Warning
otebook 6.5.7 requires pyzmq, which is not installed.
jupyter-server 1.24.0 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.

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


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:

🦉 Directory Traversal

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-JUPYTERSERVER-17152947
@anaconda-security-bot

Copy link
Copy Markdown
Author

Merge Risk: High

This is a major version upgrade from 1.x to 2.x, which introduces significant new features and breaking changes, particularly for custom extensions and configurations.

Key Breaking Changes:

  • Python Version: Support for Python 3.7 and older is dropped. The 2.x series requires Python 3.8 or newer.
  • Custom Kernel Managers: If you have extended the default KernelManager with custom functionality, you must update your code to derive from the new jupyter_server.kernel.manager.ServerKernelManager class.
  • New APIs: Version 2.0 introduces new, pluggable APIs for Identity, Authorization, and Kernel WebSockets. While these are new features, they represent a new pattern for customizing the server and may impact non-standard customizations.
  • Terminals as an Extension: The terminals service is now a server extension. It remains enabled by default, so this is unlikely to impact most users but is a structural change.

Recommendation:

Before merging, developers should verify that their environment uses Python 3.8+. If you use any custom extensions, especially those that interact with kernel management, they must be reviewed for compatibility with Jupyter Server 2.x. Check your server configurations to ensure they do not rely on deprecated classes or settings from older versions.

Source: Jupyter Server 2.0 Release Announcement

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants