[Snyk] Fix for 1 vulnerabilities

[anaconda-security-bot]

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

Snyk changed the following file(s):

• packages/tree-extension/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Handling of Case Sensitivity SNYK-JS-FASTURI-19846649	601

Breaking Change Risk

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.

---

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.

[anaconda-security-bot]

The upgrade of @jupyter-notebook/tree to version 7.0.0 is a major architectural overhaul with significant breaking changes. The other packages are minor updates from pre-releases to stable versions and are considered low risk.

@jupyter-notebook/tree@0.0.0-use.local → @jupyter-notebook/tree@7.0.0

Risk: HIGH

This upgrade is part of the new Jupyter Notebook 7 release, which is now built using JupyterLab components. This is a fundamental shift from previous versions and introduces major breaking changes, especially for customizations and extensions.

Key Breaking Changes:

• Extension Incompatibility: Classic Notebook extensions (for versions 6.x and older) are not compatible with Notebook 7. Any existing frontend extensions must be migrated to the new JupyterLab extension system or replaced with compatible alternatives.
• Server Backend: The server has moved from the classic notebook server to jupyter-server, which may break existing server extensions. A migration guide is available for this transition.
• Customization: Custom CSS and other UI customizations may no longer work and will need to be adapted to the new architecture.

While the core document-centric user experience is preserved, the underlying technology is completely different. The 0.0.0-use.local version indicates a non-standard build, making this upgrade a move to an entirely new application.

Recommendation:
Developers must review all existing Jupyter Notebook extensions and customizations for compatibility with Notebook 7. Refer to the official migration guide for detailed instructions. For critical workflows dependent on older extensions, the nbclassic package can be used as an interim solution to maintain the classic environment.

Other Upgrades

• @jupyterlab/apputils: 4.6.0-alpha.3 → 4.6.0
• @jupyterlab/mainmenu: 4.5.0-alpha.3 → 4.5.0
• @jupyterlab/services: 7.5.0-alpha.3 → 7.5.0
• @jupyterlab/settingregistry: 4.5.0-alpha.3 → 4.5.0

Risk: LOW

These are all promotions from an alpha pre-release to a final stable version. These updates consist of bug fixes and stabilization and do not introduce breaking changes.

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