(Alpha) version compatible with JupyterLab 4?

[bollwyvl]

Problem

When building jupyterlab 4.0.0a31:

conda-forge/jupyterlab-feedstock#350 (comment)

+ jupyter labextension list
JupyterLab v4.0.0a31
/home/conda/feedstock_root/build_artifacts/jupyterlab_1668971729072/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/share/jupyter/labextensions
        jupyterlab_pygments v0.2.2 enabled  X (python, jupyterlab_pygments)


"[email protected]" is not compatible with the current JupyterLab
Conflicting Dependencies:
JupyterLab              Extension               Package
>=4.0.0-alpha.16 <4.1.0 >=3.1.0 <4.0.0          @jupyterlab/application

Proposed Solution

Get an alpha out that lab4 can start building against.

Additional context

• may be relevant to break up in recursive package dependencies #23

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[RRosio]

I've been trying to update some extensions to the latest alpha version of JupyterLab 4 and in doing so ran into this message. I stated updating the JupyterLab version on my fork, but if there is a possibility that we can get an official release of an alpha version of jupyterlab_pygments that would be great!

[martinRenou]

Great! Would you like to open a PR from your branch @RRosio ?

[RRosio]

Great! Would you like to open a PR from your branch @RRosio ?

Yes, I have opened a draft PR #30, and am waiting for the results of the CI checks!

[parmentelat]

I'd like to +1 an alpha release

the worrying message

        jupyterlab_pygments v0.2.2 enabled  X (python, jupyterlab_pygments)

shows up immediately after a basic pip install jupyterlab

my feeling is it might be a red herring (as I am seeing other issues here and there with jlab4&nb7), but I can't tell for sure

[frenzymadness]

In Fedora Linux we already have JupyterLab 4 so I'm not able to update jupyterlab_pygments as an RPM package. New release compatible with the latest jupyterlab would be great.

[krassowski]

A help with configuring releaser tokens for jupyterlab-pygments would be appreciated! Specifically I cannot upload the new version to either PyPI nor npm, c-f #39 and the issue with rights in the new jupyter org. Alternatively, someone who has the rights can make the release manually.

[martinRenou]

I'll make a manual release. Let's rename the NPM package after the release.

[krassowski]

Thank you @martinRenou!

Closing as 0.3.0 is now available on PyPI https://pypi.org/project/jupyterlab-pygments/0.3.0/, and confirmed to install well:

        jupyterlab_pygments v0.3.0 enabled OK (python, jupyterlab_pygments)