-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Release 0.6.2 #1441
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
Release 0.6.2 #1441
Conversation
|
@UziTech Would you consider both #1438 and #1439 semver patches? The changes we've merged so far were fixes for regressions so I feel like we can ship a patch asap for the Node Docs team. /cc @joshbruce |
|
Ya they are definitely patches. They both fix rare conditions that would be considered broken if anyone stumbled upon them. |
|
@UziTech Is this still considered a patch release? Security
Fixes
Enhancements
CLI
Testing
|
|
I think it still is a patch release. I don't see anything that will break current workflows. |
|
@davisjam @joshbruce can we get another approval so we can release a new version? |
|
Published as |
Release 0.6.2
Publisher
$ npm versionhas been run.masterwith correct version number.$ npm publishhas been run.Note: If merges to
masteroccur after submitting this PR and before running$ npm pubishyou should be able toupstream/master(git pull upstream master) into the branch holding this version,$ npm run buildto regenerate theminfile, andCommitter
In most cases, this should be someone different than the publisher.
package.jsonhas been updated (see PUBLISHING.md).marked.min.jshas been updated; or,