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
1.0a3 prerelease #6184
Comments
Output from % python scripts/milestone_check.py master Congratulations! All PRs in this milestone have commits in the commit history for this version range, so they all probably belong in this milestone. The following commits are not included in any PR on this milestone. 4a6473e Merge pull request #6139 from minrk/referer Try checking these PRs. They probably should be in the milestone, but probably aren't: 4a6473e Merge pull request #6139 from minrk/referer |
Fixed a bunch of milestones, new output as below. It seems that all the commits listed were indeed pushed to master, so we've caught everything this script pointed out. % python scripts/milestone_check.py master Congratulations! All PRs in this milestone have commits in the commit history for this version range, so they all probably belong in this milestone. The following commits are not included in any PR on this milestone. bbc1bbd kick ci |
The prerelease, jupyterlab 1.0.0a3, is now published to pypi. |
Here is the loghub output for all PRs merged after 1.0a1. These should be merged into the current changelog in appropriate places. (for reference: PRs that were merged after 1.0a1
|
I added these changelog entries to the changelog in #6198. I think we can close this issue when that PR is merged. |
This tracks the 1.0a3 prerelease.
Some breaking changes to note:
require
, you need to dorequire('file').default
to get the content. From Update webpack #6189Here are the PRs merged in 1.0a2 or 1.0a3, not including the ones from 1.0a1 or earlier:
https://github.com/jupyterlab/jupyterlab/pulls?q=is%3Apr+is%3Amerged+merged%3A%3E2019-02-05+closed%3A%3C%3D2019-04-12+sort%3Acreated-asc
(This was going to be 1.0a2, but there were some issues with that release, so we had 1.0a3 as a quick followup release.)
The text was updated successfully, but these errors were encountered: