Release blog post improvements; @author parsing and notable header #576
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- handle @author parsing when using . instead of , in the release version header - ensure ### prefixed Notable changes header - bumped changelog-url version too handle new v0.10.x releases Refs: #551 (comment) Fixes: #553 (comment)
|
LGTM :) |
|
see also #566 |
|
LGTM! |
|
neato, lgtm, thanks @phillipj |
|
@Fishrock123 aaaah, I didn't catch that issue last week, just noticed it while doing a test run yesterday. This script shouldn't get in the way when you cut releases, so loosening up parsing seems okay to me. |
phillipj
added a commit
that referenced
this pull request
Mar 15, 2016
Release blog post improvements; @author parsing and notable header
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some improvements to the release blog post script.
Refs: #551 (comment)
Fixes: #553 (comment)
/cc @nodejs/release