chore(deps): update dependency jupyterlite-core to >=0.4,<0.5 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jupyterlite-core	>=0.3,<0.4 -> >=0.4,<0.5

GitHub Vulnerability Alerts

GHSA-gj55-2xf9-67rq

Impact

The vulnerability depends on user interaction by opening a malicious notebook with Markdown cells, or Markdown file using JupyterLab preview feature.

A malicious user can access any data accessible from JupyterLite and perform arbitrary actions in JupyterLite environment.

Patches

JupyterLite 0.4.1 was patched.

Workarounds

There is no workaround for the underlying DOM Clobbering susceptibility. However, select plugins can be disabled on deployments which cannot update in a timely fashion to minimise the risk. These are:

• @jupyterlab/mathjax-extension:plugin - users will loose ability to preview mathematical equations
• @jupyterlab/markdownviewer-extension:plugin - users will loose ability to open Markdown previews
• @jupyterlab/mathjax2-extension:plugin (if installed with optional jupyterlab-mathjax2 package) - an older version of the mathjax plugin for JupyterLab 4.x

To disable these extensions populate the disabledExtensions key in jupyter-config-data stanza of jupyter-lite.json as documented on https://jupyterlite.readthedocs.io/en/stable/howto/configure/config_files.html#jupyter-lite-json

{
  "jupyter-lite-schema-version": 0,
  "jupyter-config-data": {
    "appName": "My JupyterLite App",
    "disabledExtensions": [
      "@​jupyterlab/markdownviewer-extension:plugin",
      "@​jupyterlab/mathjax-extension:plugin",
      "@​jupyterlab/mathjax2-extension:plugin"
    ]
  }
}

To confirm that the plugins were disabled manual inspection of the built page is required.

References

Upstream advisory: GHSA-9q39-rmj3-p4r2

Notes

This change has a potential to break rendering of some markdown. There is a setting in Sanitizer which allows to revert to the previous sanitizer settings (allowNamedProperties).

---

Release Notes

jupyterlite/jupyterlite (jupyterlite-core)

v0.4.1

Compare Source

(Full Changelog)

Maintenance and upkeep improvements

• Update to JupyterLab 4.2.5 and Notebook 7.2.2 #​1473 (@​jtpio)
• Fix tbump rule #​1446 (@​jtpio)

Documentation improvements

• Update Vercel Setup Instructions for Node.js v20 #​1450 (@​michaelweinold)
• docs: update config file example with correct output dir parameter name #​1443 (@​zonca)

Contributors to this release

(GitHub contributors page for this release)

@​github-actions | @​jtpio | @​michaelweinold | @​zonca

v0.4.0

Compare Source

(Full Changelog)

Enhancements made

• Update to JupyterLab 4.2.4 #​1439 (@​jtpio)
• Update to JupyterLab 4.2.3 #​1425 (@​jtpio)
• Reduce final package size, start updating demo #​1423 (@​bollwyvl)
• Update to JupyterLab 4.2.2 #​1420 (@​jtpio)
• Update to Jupyterlab 4.2.1 #​1400 (@​jtpio)
• Add @jupyterlab/terminal-extension #​1397 (@​jtpio)
• DriveFS: Handle receiving a stream instead of a node #​1395 (@​martinRenou)
• Allow providing your own ContentsAPI implementation for the emscripten DriveFS #​1383 (@​martinRenou)
• Update to JupyterLab 4.2 and Notebook 7.2 #​1376 (@​jtpio)

Bugs fixed

• Fix some drive methods return types #​1418 (@​martinRenou)

Maintenance and upkeep improvements

• Updated integration tests workflow #​1434 (@​krassowski)
• Remove pin on importlib_metadata #​1426 (@​jtpio)
• Add packageManager to package.json #​1419 (@​jtpio)
• Bump ws from 8.13.0 to 8.17.1 in /ui-tests #​1417 (@​dependabot)
• Bump ejs #​1392 (@​jtpio)
• Fix playwright update workflow #​1391 (@​jtpio)
• Update UI-tests snapshots #​1390 (@​martinRenou)
• Bump some dependencies #​1389 (@​jtpio)
• Bump tar from 6.1.15 to 6.2.1 in /ui-tests #​1367 (@​dependabot)
• Update releaser workflows #​1356 (@​jtpio)

Documentation improvements

• Mention file access via SharedArrayBuffer in the migration guide #​1442 (@​jtpio)
• Mention jupyterlite-pyodide-kernel supports the SharedArrayBuffer in the documentation #​1428 (@​jtpio)
• Add docs about the use of SharedArrayBuffer #​1405 (@​jtpio)
• Add note about currentChanged to the migration guide #​1394 (@​jtpio)
• Typo in RTD link in index page #​1380 (@​afshin)
• [DOCS]: Suggest to wait for kernel starting to prevent to prevent "Fi… #​1372 (@​Carreau)

API and Breaking Changes

• DriveFS: Handle receiving a stream instead of a node #​1395 (@​martinRenou)

Contributors to this release

(GitHub contributors page for this release)

@​afshin | @​bollwyvl | @​Carreau | @​dependabot | @​github-actions | @​jtpio | @​juntyr | @​krassowski | @​martinRenou

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock

Updating dependencies
Resolving dependencies...

Creating virtualenv ibis-framework-3Icqsljt-py3.12 in /home/ubuntu/.cache/pypoetry/virtualenvs

Because no versions of jupyterlite-pyodide-kernel match >0.3,<0.3.1 || >0.3.1,<0.3.2 || >0.3.2,<0.4
 and jupyterlite-pyodide-kernel (0.3.0) depends on jupyterlite-core (>=0.3.0,<0.4.0), jupyterlite-pyodide-kernel (>=0.3,<0.3.1 || >0.3.1,<0.3.2 || >0.3.2,<0.4) requires jupyterlite-core (>=0.3.0,<0.4.0).
And because jupyterlite-pyodide-kernel (0.3.1) depends on jupyterlite-core (>=0.3.0,<0.4.0)
 and jupyterlite-pyodide-kernel (0.3.2) depends on jupyterlite-core (>=0.3.0,<0.4.0), jupyterlite-pyodide-kernel (>=0.3,<0.4) requires jupyterlite-core (>=0.3.0,<0.4.0).
So, because ibis-framework depends on both jupyterlite-core (>=0.4,<0.5) and jupyterlite-pyodide-kernel (>=0.3,<0.4), version solving failed.

[github-actions]

ACTION NEEDED

Ibis follows the Conventional Commits specification for release automation.

The PR title and description are used as the merge commit message.

Please update your PR title and description to match the specification.

[cpcloud]

Closing in favor of #10052.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (>=0.4,<0.5). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.