-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Implement 2.0.0 breaking changes #6713
Conversation
OK, we now have a pre-release of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM to merge then.
191a578
to
5a9858c
Compare
Thank you, @chrisdavidmills! I have since updated the base branch from |
This concludes the `mdn-` package name and continues development under the `@mdn/browser-compat-data` name. * Implement 2.0.0 breaking changes (#6713) * Rename package and increment version to pre-2.0 * Require Node 10 or later * Rename package in the docs * Increment prerelease version * Initial release of @mdn/browser-compat-data A continuation of mdn/browser-compat-data * Patch release containing data or non-breaking updates only * Revert "Add mdn- and Node.js 8 deprecation warnings for 1.1 release (#6777)" This applies only to the 1.1.x releases. This reverts commit ee7feac. * Patch release containing data or non-breaking updates only * Patch release containing data or non-breaking updates only * Use Node.js ≥10 for CI and drop Travis (#6797) * Use Node.js ≥10 for CI * Remove Travis CI config * Remove badges from README * Patch release containing data or non-breaking updates only
This is one of several ugly steps to carry out #6640.
This PR does two key things:
master-scoped-package
.mdn-browser-compat-data
An additional ugly thing I'm going to do is a pre-release from this branch (i.e.,
ddbeck-2.0-breaking-changes
) before merging to demonstrate that, well, it works as a new package. This will also test the new packaging workflow before I release BCD 1.0.38 today.