-
Notifications
You must be signed in to change notification settings - Fork 945
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
7.6.0 release notes #3048
Comments
We should probably annotate the changelog with a note that widget extension authors wanting to support JupyterLab 3 should add the "jupyterlab": {
"sharedPackages": {
"@jupyter-widgets/base": {
"bundled": false,
"singleton": true
}
}
} as noted in the jupyterlab docs: https://jupyterlab.readthedocs.io/en/stable/extension/extension_dev.html#requiring-a-service |
@jasongrout I'm a bit confused why stable has documentation for 7.6 but the latest docs do not. I just spent a bunch of time trying to find up-to-date release notes in |
Related -- are there any additional changelog notes for non-jupyterlab users of widgets? We're having difficulty debugging issues with Output widgets in nteract and don't know if there's contract changes we should be aware of outside of the extension system. |
Master is tracking development of the forthcoming ipywidgets 8.0, which has stalled for a long time. The active work on 7.x is going on the 7.x branch. It's an unfortunate bifurcation of the branches and development effort stemming from the 8.0 release stalling out, but still needing updates to the existing 7.x line. We're setting up a meeting in the next few weeks to restart effort on ipywidgets 8, and one of the first items to do is to migrate changes (like the changelog entries!) from the 7.x branch to master. |
@jasongrout Thanks. Can you make sure that @MSeal, @captainsafia, and I are made aware of the upcoming meeting? It's great to see progress being made. I do think that there is a fair amount of confusion currently for non-JupyterLab frontends or applications since there isn't a real clear chart on which npm packages have support for something and which can be used together. Any thoughts on how to pull this info together easily and keep it updated as widgets evolve? |
The output widget interface has been really stable. Here is the list of commits from that package (notice it is the 7.x branch, not master): https://github.com/jupyter-widgets/ipywidgets/commits/7.x/packages/output You can see we've just been publishing new versions as the underlying |
That sounds like an excellent topic to discuss in the meeting! |
8.0 release discussion is on #2750 The upcoming meeting whenisgood poll and agenda are noted at #2750 (comment) |
Following up on this: this is done in #3051 |
Thanks @jasongrout. I appreciate the response 👍🏼 |
Seconded and the response. Thanks for engaging on those points |
Great. Closing this issue as resolved, and we can continue conversation on the 8.0 issue. Thanks! |
We released ipywidgets 7.6.0 today.
It turns out that lerna isn't as able to bump rc versions of packages as I remember. In order to do the 7.6 release, I did:
This bumped the versions of appropriate packages from rc to final releases and published them.
The text was updated successfully, but these errors were encountered: