Skip to content
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

react-select version screwed up #1195

Closed
wants to merge 1 commit into from

Conversation

juliankrispel
Copy link
Contributor

it was 1.0.0-rc.1 should be 1.0.0-rc

it was `1.0.0-rc.1` should be `1.0.0-rc`
@juliankrispel
Copy link
Contributor Author

cc @JedWatson

@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.892% when pulling 64aff65 on juliankrispel:patch-1 into fa569e1 on JedWatson:master.

@bvaughn
Copy link
Collaborator

bvaughn commented Sep 13, 2016

Why do you feel it should be one vs the other? This version numbering allows us to release multiple release candidates (eg rc.1, rc.2, etc) in a way that NPM will handle gracefully.

Regardless, the release has been published to NPM and so it cannot be changed now. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants