New release required for jupyter-standaloneproxy

[dometto]

Hello and thanks for all the hard work! The work to integreate jupyter-standaloneproxy into this project is amazing and very helpful. However, the (live) docs currently state that one should be able to: pip install jupyter-server-proxy[standalone]. This is a littel confusing, as this currently does not work:

warning: The package jupyter-server-proxy==4.4.0does not have an extra namedstandalone``

It does work when I install the latest version of this package diretly from github:

uv pip install "git+https://github.com/jupyterhub/jupyter-server-proxy.git[standalone]"

I suppose a new release is required before jupyter-server-proxy[standalone] is published. Can we expect a new release in the near future?

[dometto]

Ping?

[dometto]

@minrk -- is there a schedule for a new release to PyPi?

[jhgoebbert]

@manics Can you create a new release for jupyter-server-proxy?

[jwindgassen]

Also just bumping this, we would appreciate a proper release.

[manics]

Can someone make a start on the first two steps of the release process? Open PRs to update yarn.lock, and to update the changelog using github-activity (usually requires some manual cleanups):
https://github.com/jupyterhub/jupyter-server-proxy/blob/main/RELEASE.md#steps-to-make-a-release

[ryanlovett]

@manics The current version is 4.4.1-0.dev, but #521 was marked "API and Breaking Changes" by github-activity. However your comment suggested otherwise. Should we go to 4.4.1 or 4.5.0?

[minrk]

@manics had pointed out that it wasn't breaking because the things it broke hadn't been released. I've updated the label accordingly.

[minrk]

oh: let's go for 4.5.0, there is some good new stuff in there, especially #501

I added a few more missing PR labels

[jwindgassen]

@manics The first 2 steps are done!

[ryanlovett]

I tagged a release, but the npm publish action failed. The token may have expired (last successfully published 2 years ago) or it may no longer have publish permissions. I don't have the collaborator role at npmjs.com to update NPM_TOKEN. I'll ping a few of folks that do.

[ryanlovett]

@minrk enabled trusted publishing for npmjs. I moved the tag for v4.5.0 to point to 3e4ff45 and that kicked off publishing again. The pypi publishing failed the second time because the python package was already published, but npmjs succeeded.

So the latest release is out. Thanks @dometto, @jwindgassen, and @minrk !