Update to React 0.11

[glittershark]

No description provided.

[WickyNilliams]

👍 keen to move to react 0.11.0

[WickyNilliams]

Might it be worth setting version to something like ">= 0.11.0" (as is done here in reactify)? That way it won't be tied to a specific version and you won't need to update for each release?

[glittershark]

Semver says minor version = potentially breaking change. imo it's best
to conform to that.

On 07/18, Nick Williams wrote:

Might it be worth setting version to "^0.11.0"? That way it will be considered compatible with anything up to 1.0.0 (which, for the most part, is unlikely to have breaking changes)

---

Reply to this email directly or view it on GitHub:
#33 (comment)

Griffin Smith
[email protected]
(720) 206-7218

[ericclemmons]

I thought minor was:

MINOR version when you add functionality in a backwards-compatible manner

So should we use ^0.11.0?

http://fredkschott.com/post/2014/02/npm-no-longer-defaults-to-tildes/

[WickyNilliams]

See semver.org:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.

However, below 1.0.0 everything is considered unstable. For that reason ^ has a special meaning below < 1.0.0. That's explained here: https://www.npmjs.org/doc/misc/semver.html

^0.1.3 := >=0.1.3-0 <0.2.0-0 "Compatible with 0.1.3". 0.x.x versions are special: the first non-zero component indicates potentially breaking changes, meaning the caret operator matches any version with the same first non-zero component starting at the specified version.

[ericclemmons]

So ^0.11.0 would match >=0.11.0-0 <0.12.0-0. That's what we'd want, right? It means we'd have to manually bump with each minor react version until they hit 1.0, but that seems right...

You tell me :)

[larsonjj]

^0.11.0 would be correct. You will have to update the dependency for react again when they hit 0.12.0, but that will ensure that this module will not break anyone's builds on the next update. Not ideal, but it seems to be the correct way to go about it.

[WickyNilliams]

Yeah i think you're right, >= is too permissive while React is < 1.0.0

[glittershark]

I just fixed the PR to use ^0.11.0

[WickyNilliams]

[ericclemmons]

v0.8.3 is out with it!

Thanks!

[glittershark]

Yay, thanks!

[larsonjj]

👍