-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
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
v2023.06.30 mysteriously appeared and pins jupyterlab<4 #159
Comments
I'm on mobile so it is hard to find things but it seems that the pangeo bot updated it, no? |
ugh, I was experimenting with this on the GitHub UI, and realized I should stop when it by default created a branch in the same repo than in my fork! I killed it before it made the PR, thinking that would prevent anything bad from happening :( I figured I'd come back to it after this weekend, but apparently just me editing and creating the branch made the package :( Sorry everyone! |
jupyterlab-git (jupyterlab/jupyterlab-git#1245) and possibly other extensions no longer worked because of the 4.0 migration, which was my reason for poking at this. |
0726a9e was the commit. |
All good! I'm just glad to know that I'm not going crazy :) |
Solution to issue cannot be found in the documentation.
Issue
I noticed there is pangeo-notebook=2023.06.30 on conda-forge, but no corresponding tag in this repository.
pangeo-notebook-feedstock/recipe/meta.yaml
Line 18 in a1b2d40
mamba search pangeo-notebook --info
Can anyone help identify how that got there? cc @yuvipanda @ocefpaf
The text was updated successfully, but these errors were encountered: