An in-range update of react-router-dom is breaking the build 🚨

[greenkeeper]

Version 4.2.0 of react-router-dom just got published.

Branch	Build failing 🚨
Dependency	react-router-dom
Current Version	4.1.2
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

react-router-dom is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v4.2.0

Changes

Aug 23, 2017

• Re-run Redirect on props update (#5162 by @alexilyaev)
• Prevent remounts on routes with the same component in renderRoutes (#5430 by @artywhite)
• Case sensitive routes (#5438 by @paustria)
• Use direct imports in platform packages (#5095 by @ruiaraujo)
• Add optional otherProps argument renderRoutes (#5137 by @jharris4)
• Bump hoist-non-react-statics (#5347 by @roderickhsiao)
• 3x build speed improvements on CI (ea1212a by @timdorr)
• Use Jest for testing (172dc16 by @mjackson)
• Explicit error using Route outside of Router (#4939 by @eXon)
• react-router-native Link improvements (#4816 by @benstepp)
• aria-current on NavLink (#4708 by @JasonEtco)
• Make AndroidBackButton a generic BackButton component (#5295 by @DonnieWest)
• Access Link's underlying node via innerRef (#5294 by @danielberndt)
• Return null from react-router-native DeepLinking if children is undefined (#5278 by @seekshiva)
• Warn when using the history prop on a pre-configured Router (#5151 by @Aprillion)
• Fix memory leak in ConnectedRouter during server side rendering (#5203 by @klis87)
• Reorder NavLink activeClassName/className priority (#5109 by @carloluis)
• Change react-native BackAndroid to BackHandler (#5093 by @SeanGroff)
• Fix react-router-native StackRouter (#5071 by @kafein)

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 4.1.2 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper]

Version 4.2.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

react-router-dom v4.2.1

This fixes a missing warning dependency if you were installing just react-router-dom. No other changes to the actual code.

[greenkeeper]

Version 4.2.2 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

react-router-dom v4.2.2

Apologies for the quick rebuild. There was a bad UMD config, which would have required you to include both the react-router and react-router-dom UMD files. You should only have to include react-router-dom now, which is the same behavior as the npm package.

OK, I'm done for a bit... 😬

[greenkeeper]

Version 4.3.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

v4.3.0

The major new things of this release are Redirect with params (see #5209) and the new generatePath API. We also cleaned up the code with Prettier, so browsing through it should be more enjoyable.

One other thing to mention, while I have your attention, is the deprecation of react-router-redux. It's no longer maintained and has a number of fundamental problems (particularly around time travel). Integrating Redux and the DOM History API is challenging because they don't maintain the same semantics and the resulting integration is error prone. Getting to the router context will be easier in future versions of React Router, so the main motivations for needing it will be going away. So, while I would advise against trying to integrate the two, for those that still want this functionality can turn to libraries like @supasate's connected-react-router.

Changes

• Use the pretty option in generatePath (#6172 by @sibelius)
• aria-current has incorrect value "true" (#6118 by @brandonrninefive)
• Redirect with parameters (#5209 by @dlindenkreuz)
• Fix with missing pathname: <Link to="?foo=bar"> (#5489 by @pshrmn)
• Escape NavLink path to allow special characters in path. (#5596 by @esiegel)
• Expose generatePath (#5661 by @rybon)
• Use named import of history module. (#5589 by @RoboBurned)
• Hoist dependencies for smaller UMD builds (#5720 by @pshrmn)
• Remove aria-current from navLink when inactive (#5508 by @AlmeroSteyn)
• Add invariant for missing "to" property on <Link> (#5792 by @selbekk)
• Use Prettier on the code (e6f9017 by @mjackson)
• Fix pathless route's match when parent is null (#5964 by @pshrmn)
• Use history.createLocation in <StaticRouter> (#5722 by @pshrmn)

[greenkeeper]

Version 4.3.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

v4.3.1

Just a patch to fix an accidental move of warning from a normal dependency to a devDependency, which was causing issues with installation.

[greenkeeper]

• The dependency react-router-dom was updated from 4.3.0 to 4.3.1.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for v4.4.0-beta.5

One step closer to 4.4.0 final...

Fixes

• Fixed <Route component> prop-type warning when using forwardRef (see #6417, thanks @frehner and @eXon)
• Added missing file to react-router-config package (see #6415, thanks @Anomen)
• Several docs improvements (see #6410, thanks @justsml)

Enjoy! 😅

[greenkeeper]

• The dependency react-router-dom was updated from 4.3.1 to 4.4.0.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀