greenkeeper[bot]
commented
6 years ago After pinning to 4.2.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Open greenkeeper[bot] opened 6 years ago
greenkeeper[bot]
commented
6 years ago After pinning to 4.2.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
greenkeeper[bot]
commented
6 years ago Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Just a patch to fix an accidental move of warning from a normal dependency to a devDependency, which was causing issues with installation.
greenkeeper[bot]
commented
5 years ago 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 🚀
Version 4.3.0 of react-router-dom was just published.
react-router-domThis 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, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/TEDxKasetsartU/TedXKasetsartU-Frontend/327?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)Release Notes
v4.3.0The major new things of this release are Redirect with params (see #5209) and the new
generatePathAPI. 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
prettyoption in generatePath (#6172 by @sibelius)<Link to="?foo=bar">(#5489 by @pshrmn)generatePath(#5661 by @rybon)<Link>(#5792 by @selbekk)<StaticRouter>(#5722 by @pshrmn)FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: