Prepare for 0.23 release

Author: STRML

README.md

@@ -1,6 +1,7 @@
 # React Router Component
 
-For React 0.12 support, see the [react-0.12](https://github.com/STRML/react-router-component/tree/react-0.12) branch. It should be stable, but please help us bugtest it.
+*React-Router-Component >= 0.23 uses React 0.12. If you need React 0.11 support,*
+*please use versions 0.20 through 0.22.2.*
 
 React router component allows you to define routes in your [React][] application
 in a declarative manner, directly as a part of your component hierarchy.
@@ -49,7 +50,7 @@ React router component is packaged on npm:
 
 ## Compatibility
 
-Compatible with React 0.10 and 0.11. Support for 0.12 is experimental. See the [branch](https://github.com/STRML/react-router-component/tree/react-0.12).
+Compatible with React 0.12. Older versions work with older versions of React, see the commit log.
 
 See [docs][] for the usage.
 

tests/browser.js

@@ -93,9 +93,13 @@ describe('Routing', function() {
  path: '/__zuul',
  foo: 'bar',
  ref: 'link',
+ // To reach through a Location boundary, you must put a ref
+ // on the Location itself, and the handler. We used to be able to just clone
+ // the handler with the ref, but React now throws warnings on that use.
  handler: React.createClass({
  render: function() {
  return Link({
+ ref: 'inner',
  foo: this.props.foo,
  href: '/__zuul/hello'
  }, 'mainpage')
@@ -226,7 +230,7 @@ describe('Routing', function() {
 
  it('navigates via .navigate(path) call', function(done) {
  assertRendered('mainpage');
- router.refs.link.navigate('/__zuul/hello', function() {
+ router.refs.link.refs.inner.navigate('/__zuul/hello', function() {
  assertRendered('hello');
  done();
  });