Release latest pre-releases on conda-forge

[andrii-i]

Problem

Latest version of jupyter-chat released on conda-forge is 0.19 (https://github.com/conda-forge/jupyterlab-chat-feedstock/blob/main/recipe/recipe.yaml) so latest pre-releases are not available for download from conda-forge.

Proposed Solution

Release 0.20.0a2 (or latest pre-release) on conda-forge, continue releasing new versions on conda-forge in-sync with PyPI releases.

[dlqqq]

Thanks for opening this issue Andrii! Wanted to elaborate a bit here:

Pre-releases are tricky because annoyingly, Conda Forge insists that they are published to a separate channel: https://github.com/conda-forge/cfep/blob/main/cfep-05.md. You would have to add this channel configuration before publish a pre-release, then remove it after publishing an official release, etc. To be completely honest, I understand that publishing pre-releases on CF is not worth the effort.

However, we're in the process of releasing Jupyter AI subpackages onto Conda Forge, but the issue is that some of these packages depend on v0.20 pre-releases for some new features like Andrii's recent message metadata addition. We can't release until those changes are available in CF.

I'm wondering: is there a reason v0.20 is still in pre-release? And also, can we stick to publishing official releases if there are no known bugs when the release is published? Patch releases can be used to fix any bugs introduced by a minor release. That would be super helpful - we would be able to push out Jupyter Chat & Jupyter AI v3 to Conda Forge users faster. 😄

[dlqqq]

cc @brichet

[brichet]

Thanks for opening this @andrii-i.
The main reason for waiting is the change of the side panel UI/UX #343.
It change the handling of side panel chats, we probably need to make sure that it doesn't break anything before releasing it.

I haven't seen issue with jupyterlab-chat so far, I don't think that there will be issue with jupyter-ai.
We are currently testing its integration in jupyterlite-ai in jupyterlite/ai#278.

[brichet]

And also, can we stick to publishing official releases if there are no known bugs when the release is published? Patch releases can be used to fix any bugs introduced by a minor release.

👍 we should probably release that way again.
Let's make sure that #343 is fine and let's move forward with an official 0.20.0.

[dlqqq]

Awesome, TYSM! 🙌

[brichet]

To follow up, IMO we can make a v0.20.0 release after #376 and #377, which are both approved.

@jtpio do you think of other changes that should be included ?

[jtpio]

Yes releasing 0.20.0 sounds good after these PRs are merged 👍

Unfortunately releases are currently still blocked by (hopefully just a matter of waiting a couple of hours at most):

• check-release action is failing jupyter-server/jupyter_releaser#645
• Hatch v1.16.5 is not available in PyPI pypa/hatch#2198

[jtpio]

Looks like hatch is fixed now. Will look into releasing 0.20.0 in the coming days.

[jtpio]

Closing as fixed by conda-forge/jupyterlab-chat-feedstock#5