-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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 v0.5.2 #1365
Release v0.5.2 #1365
Conversation
Looks like jasmine broke compatibility with older versions of node recently. I created a PR but I'm not sure many packages support Node < v4 |
looks like tests are failing because Jasmine just released v3.3.0 which is not compatible with node v0.10 we could fix this by pinning our jasmine dev dependency to v3.2.0 or remove node v0.10 from travis |
to be honest if any of our dependents are still using node v0.10 they are probably the ones pinning their marked dependency to 0.3.6 |
according to https://libraries.io/npm/marked/usage we have less than 400 dependents using >=0.5.0 and ~1000 using >=0.4.0 |
2118d9c
to
1b7598d
Compare
Release NotesBug Fixes
Other
|
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.
Do eet!
Release v0.5.2
Publisher
$ npm version
has been run.master
with correct version number.$ npm publish
has been run.Note: If merges to
master
occur after submitting this PR and before running$ npm pubish
you should be able toupstream/master
(git pull upstream master
) into the branch holding this version,$ npm run build
to regenerate themin
file, andCommitter
In most cases, this should be someone different than the publisher.
package.json
has been updated (see PUBLISHING.md).marked.min.js
has been updated; or,