Jeremy Tuloup

@martinRenou just checking if this PR is ready to go?

Maybe we can add a quick note to the migration guide, since this might cause a change of behavior in some cases? https://jupyterlite.readthedocs.io/en/latest/migration.html#to-0-4-0

Trying this locally, it looks like the error is raised even when running a `jupyter lite build` without the `--conents` option.

Converting back to draft as it would be great to: - only raise the error if `contents` is specified but `jupyter-server` is not installed - add a test

Bumping to `0.5.0` to avoid a change of behavior, until we figure out a good way to raise this error smoothly.

> I guess this issue is about whitelisting the favicon.ico file by default? I think so yes. Especially if the warning is constantly in the logs.

Classic tokens are going to be retired very soon: https://github.blog/changelog/2025-09-29-strengthening-npm-security-important-changes-to-authentication-and-token-management/ So we should look into supporting trusted publishers as soon as possible here in the releaser to lower friction and...

Tried again with a JupyterLab extension, and it seems the missing piece was to make sure `npm` 11.5.1 or higher is installed: ``` npm install -g npm@latest ```

> `npm install -g npm@latest` An alternative is to use Node.js 24 directly: ```yaml - uses: jupyterlab/maintainer-tools/.github/actions/base-setup@v1 with: node_version: '24' ``` Which includes npm 11: https://nodejs.org/en/blog/release/v24.0.0#npm-11 So, the path forward...

> alternatively, we could update the base-setup action in the maintainer tools repo to default to Node.js 24 Opened https://github.com/jupyterlab/maintainer-tools/pull/259