Release 0.5.0

Question

Release 0.5.0

Closed this issue 8 years ago · 15 comments

mikaelkaron commented 10 years ago

Would it be possible to release a 0.5.0 version?

barraponto commented 8 years ago

Oh yeah.

barraponto commented 8 years ago

Ok!

Answer 1 · 2015-05-11T14:40:21.000Z

I'm not sure what you mean. Simply update the version number? Or add new features that warrant a version release?

Scott Stanfield
scott@vertigo.com

On May 11, 2015, at 4:42 AM, Mikael Karon notifications@github.com wrote:

Would it be possible to release a 0.5.0 version?

—
Reply to this email directly or view it on GitHub.

Answer 2 · 2015-05-11T15:16:42.000Z

Was thinking of the changes in master, or am I somehow not getting the latest when I npm install markdown-to-json?

Answer 3 · 2015-05-11T15:27:27.000Z

Oh I see. That could be the case. I need to let npm know; might be different versions. Will check on that today.

Scott Stanfield
scott@vertigo.com

On May 11, 2015, at 8:16 AM, Mikael Karon notifications@github.com wrote:

Was thinking of the changes in master, or am I somehow not getting the latest when I npm install markdown-to-json?

—
Reply to this email directly or view it on GitHub.

Answer 4 · 2016-08-07T22:07:33.000Z

This don't seem to be solved? I would like to use 0.5.0 too.
Thanks!

Answer 5 · 2016-09-14T19:04:52.000Z

It's been awhile since I've used npm to publish a package. I'll look into this. In the meantime, if someone knew the steps, paste them here and I'll get on it.

Answer 6 · 2017-03-22T18:42:43.000Z

Hey @scottstanfield , we should publish an updated package soon. In the meanwhile, I've been using my own fork -- but I'd rather roll back and use the main project.

Answer 7 · 2017-03-22T18:43:25.000Z

Do you mean publish to NPM?

…

On Mar 22, 2017, at 11:42 AM, Capi Etheriel ***@***.***> wrote: Hey @scottstanfield <https://github.com/scottstanfield> , we should publish an updated package soon. In the meanwhile, I've been using my own fork ***@***.***/markdown-to-json> -- but I'd rather roll back and use the main project. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARIfMTjc88vgiZrIkyNvIzrVdUYLt_Qks5roWukgaJpZM4EWgEo>.

Answer 8 · 2017-03-22T18:44:10.000Z

ok...it's been ages. I'm happy to do it. I'll go look into it, but I kinda forgot. If you know, drop steps here. Otherwise, I'll go look!

Answer 9 · 2017-03-22T18:45:34.000Z

well, basically... change the version in "package.json", commit and tag it.
then npm publish from the command line. You might have to npm login first.

Answer 10 · 2017-03-22T18:46:29.000Z

right, the npm login. I'm also adding you as a contributor to the package.json. Thanks for keeping this going!

Answer 11 · 2017-03-22T18:49:38.000Z

Done! Published as version 0.5.0 to npm registry. Please check it out.

Answer 12 · 2017-03-22T18:49:48.000Z

Thanks for the attribution! I'm glad to help.
You may notice my fork has some more changes (using ESLint and some cosmetic functional programming changes). I can make new PRs (but they don't change anything, just makes it more "modern").

Answer 13 · 2017-03-22T18:50:35.000Z

Can you submit a PR of your fork, and I'll pull it in and bump to version 0.5.1