semantic-release always wants to publish v1.0.0 about semantic-release HOT 6 CLOSED

Thanks for the report, I'm investigating this now.

from semantic-release.

Okay given that the npm credentials were correctly setup for releasing 1.0.0 this indeed seems to be a regression (also the same and real reason for #45).

1.1.0 should have been released for 73032331d9fcece165e10a1816fe3de93ab9cd0e, and as you only pushed on 61fa7cf86528e04f4c556b4f06e472770dbc1123 it should've happened there.

74a84ce4ec9351e00d40b1f0d2daef8bdd12e887 breaks it for real though, so please revert that.

The only recent change that messed with this logic is this 3.4.0 https://github.com/boennemann/semantic-release/releases/tag/v3.4.0 (cc @christophwitzko).
Can you please pin the semantic-release dependency to 3.3.2 https://github.com/boennemann/semantic-release/releases/tag/v3.3.2 and tell me if it works then?

Thanks for your patience,

Stephan

from semantic-release.

going back to:
version: 0.0.0-semantically-released
semantic-release: 3.3.2

produced v1.1.0

from semantic-release.

@christophwitzko Do you think is related to the private module support? Can we add npm-registry-client as a quick fix here?

from semantic-release.

Alright In the meantime I've moved the latest tag on npm back to version 3.3.2 so the problematic version will no longer be installed by default. We're still looking for a fix here.

from semantic-release.

We won't fix this in the 3.x range. 4.x is due very soon.

from semantic-release.