[Snyk] Security upgrade @jupyterlab/buildutils from 4.5.0-alpha.3 to 4.6.0

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

• buildutils/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
	Access of Resource Using Incompatible Type ('Type Confusion') SNYK-JS-HANDLEBARS-15803086	738

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:

🦉 Access of Resource Using Incompatible Type ('Type Confusion')

[anaconda-security-bot]

This upgrade from a pre-release version to a stable minor release introduces significant changes to the underlying build system for JupyterLab extensions.

Key Changes:

• Build System Migration: JupyterLab's build tooling is migrating from @jupyterlab/buildutils to a new standalone package, jupyter-builder (@jupyter/builder on npm). While existing extensions are expected to continue working, the official recommendation is to migrate to the new build system.
• Rspack Build Tool: JupyterLab 4.6 will use Rspack instead of Webpack for building extensions. Most extensions should not require changes unless they use a custom Webpack configuration.
• Setuptools Dependency: JupyterLab 4.6 no longer includes setuptools as a runtime dependency. If your extension relies on setuptools for packaging or build hooks, you must now explicitly add it as a dependency.

Recommendation: Although no immediate code changes are mandatory, the underlying build system has been fundamentally changed. It is important to verify that your extension packaging and build processes are still functioning correctly after this upgrade. Consider planning a migration to the new jupyter-builder system as recommended by the developers.

Source: JupyterLab Extension Migration Guide

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