Why not release v1.0.0 on npm?

[nweldev]

I added this repo as a submodule in my project as I needed to use the programmatic API and needed to fix #20. Why not release this version, at least as @next?

[badrihippo]

@xdamman if you can't access npm (as mentioned in #20 (comment)) then perhaps you could do a "release" tag on GitHub instead?

Right now when I browse the "releases" I get only v0.1.6; I have to look through the commit log to find the newer version. It would be useful to find it in the "release" list (and who knows, maybe that's where npm gets its releases from too?).

[PatrickHeneise]

I created the release v0.2.0 from the latest master. Unfortunately I don’t have access to npm and can’t complete the semantic-release setup for automated publishing. https://github.com/xdamman/mediumexporter/releases/tag/v0.2.0

[badrihippo]

This is good enough! I can now install using

npm install github:xdamman/mediumexporter#v0.2.0

But perhaps you could change the package.json version number to match with the tag (or vice versa)? Right now npm thinks it's [email protected] even though the tag is v0.2.0.