We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Following recommendations from https://github.com/conda-forge/cfep/blob/master/cfep-05.md, we should change https://github.com/conda-forge/jupyterlab-feedstock/blob/prerelease/recipe/conda_build_config.yaml to refer to the jupyterlab_dev or jupyterlab_rc channels (or perhaps create two different branches, one for dev and one for rc). I think we should do this after 2.0 is released so we don't break the prerelease workflow for 2.0.
jupyterlab_dev
jupyterlab_rc
The text was updated successfully, but these errors were encountered:
#206 created 2.1.0rc0 on the new rc branch. I'll close the prerelease branch as obsolete now.
Sorry, something went wrong.
No branches or pull requests
Following recommendations from https://github.com/conda-forge/cfep/blob/master/cfep-05.md, we should change https://github.com/conda-forge/jupyterlab-feedstock/blob/prerelease/recipe/conda_build_config.yaml to refer to the
jupyterlab_dev
orjupyterlab_rc
channels (or perhaps create two different branches, one for dev and one for rc). I think we should do this after 2.0 is released so we don't break the prerelease workflow for 2.0.The text was updated successfully, but these errors were encountered: