publish version 1.0.0 to npm

[redchair123]

The npm version still appears to be 0.9.1

[valueof]

Once I'm done updating the website I'll publish it. 1.0.0 was tagged, not released.

[redchair123]

@antonkovalyov FYI you can also use semver-style tags in package.json (e.g. 1.0.0-beta or something). I saw the 1.0.0 and assumed that it was a proper release.

[valueof]

I know that and I used them up until RC4 (tags are still up, you can check them out). And once I was comfortable tagging it as 1.0.0 I changed the package.json version.

[redchair123]

@antonkovalyov +1 I see that now after looking at the history of package.json

[btipling]

Kinda weird to have something in master that isn't deployed. At least it's messing with people's expectations and giving you the tedious work of closing issues all the time. 🐟

You could just leave this issue open. Might save you work. 🌠 ⭐ 🌟

[valueof]

If I deployed master all the time you'd have way more JSHint versions with half of them broken.

[btipling]

Well the alternative to not deploying master all the time is using branches. A broken master is always bad in general git best practices.

[redchair123]

@antonkovalyov it might make sense to reopen this so that others see it before submitting more issues.