-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
doc: fix v6 changelog #6435
doc: fix v6 changelog #6435
Conversation
## 2009.06.11, Version 0.0.3 |
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.
added a new line at the end of the file... can pull it out
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.
that makes sense to me
LGTM |
@@ -143,84 +143,85 @@ v5.0.0 release. | |||
|
|||
Semver-major Changes since v5.0.0 | |||
|
|||
* [[`4e46931406`](https://github.com/nodejs/node/commit/4e46931406)] - **(SEMVER-MAJOR)** **src**: deprecate undocumented variables (Jackson Tian) [#1838](https://github.com/nodejs/node/pull/1838) |
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.
it looks like these are order, except for this one. Maybe move it down with the other src
commits?
LGTM with a nit |
@jasnell Might it be worth also calling out the npm change that makes npm not run unless node is in the path in the Notable Changes section? I know it was listed in the semver-major commits, but it's under tools, which makes it quite hard to spot. I understand why the change was made, but it does mean that you can no longer simply untar and then run Original PR: #6098 Commit: 8ffa20c I was going to open an issue/pull request, but as you're already making changes to the Changelog I thought it might be easier to do both together. Let me know if you'd rather I opened a separate PR. |
Not quite sure how, but quite a few of the commits were missing from the original changelog generated for v6 relative to v5.11.0. This updates the change log.
a9da515
to
29217cd
Compare
@evanlucas @gibm ... done. |
Not quite sure how, but quite a few of the commits were missing from the original changelog generated for v6 relative to v5.11.0. This updates the change log. PR-URL: nodejs#6435 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
landed in b8f035b |
Not quite sure how, but quite a few of the commits were missing from the original changelog generated for v6 relative to v5.11.0. This updates the change log. PR-URL: nodejs#6435 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
Not quite sure how, but quite a few of the commits were missing from the original changelog generated for v6 relative to v5.11.0. This updates the change log. PR-URL: #6435 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
Not quite sure how, but quite a few of the commits were missing from the original changelog generated for v6 relative to v5.11.0. This updates the change log. PR-URL: nodejs#6435 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
Checklist
Affected core subsystem(s)
doc (changelog)
Description of change
Not quite sure how, but quite a few of the commits were missing from the original changelog generated for v6 relative to v5.11.0. This updates the change log.
(would need to land on v6 also)
/cc @Fishrock123