An in-range update of react-native-rename is breaking the build 🚨

[greenkeeper[bot]]

The dependency react-native-rename was updated from 2.2.2 to 2.3.0.

🚨 View failing branch.

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

react-native-rename 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: build:** Your tests passed on CircleCI! ([Details](https://circleci.com/gh/dwmkerr/gameboard/977?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)). - ❌ **ci/circleci: ios:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/dwmkerr/gameboard/978?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).

---

Release Notes for v2.3.0

Version 2.3.0 fixes a bug in the logic for finding files to update. This should fix several issues of files not being properly updated or being removed.

Fixes:

• #59
• #57

Commits

The new version differs by 8 commits.

• b4992a3 release(2.3.0): Fix handling for file rename logic.
• fb0445d fix(rename): #57 -- allow foreign language character rename
• 51045df docs: clarify no updates to build artifacts
• 0718d63 Merge pull request #59 from ajcrites/master
• 4e1d1fa Fix logic to track modified file count
• 8a1f381 Update README.md
• 0a214cb Merge pull request #42 from knewzen/master
• 7fb9a45 remove codesponsor

See the full diff

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:

[greenkeeper[bot]]

After pinning to 2.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]]

• The dependency react-native-rename was updated from 2.3.0 to 2.3.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

• 97242f0 release(v2.3.1): Update program version number
• 3551527 Merge pull request #61 from junedomingo/acrites/53
• 20b6295 fix(rename): only replace project name in directory once.

See the full diff

[greenkeeper[bot]]

• The dependency react-native-rename was updated from 2.3.1 to 2.3.2.

Your tests are still failing with this version. Compare changes

Release Notes for v2.3.2

Fixes #63

Commits

The new version differs by 2 commits.

• 3c9ecf4 release(2.3.2): bumping version numbers
• a206795 fix(rename): transform rename regex to support node v<10

See the full diff

[greenkeeper[bot]]

• The dependency react-native-rename was updated from 2.3.2 to 2.4.0.

Your tests are still failing with this version. Compare changes

Release Notes for v2.4.0

• #55 Addresses the issue of Java source files being deleted inappropriately when using the same package name.
• #47 Also handles deleting of module files alongside common Java source files.

Commits

The new version differs by 8 commits.

• 16b2e56 Merge pull request #65 from junedomingo/release/v2.4.0
• 7e19a94 release(2.4.0): bumping version
• e82d990 fix(naming): Prevent inappropriate package name update
• bbb8bb8 release(2.4.0-rc3): updating with latest master release
• bab35b0 fix(naming): #47 -- copy over all android source content
• fff1c16 release(2.4.0-rc2): updating with latest master release
• 83d08e2 release(2.4.0-rc1): fix Java naming issues
• f94676e fix(naming): #55 -- do not delete old matching package bundle name

See the full diff

[greenkeeper[bot]]

• The dependency react-native-rename was updated from 2.4.0 to 2.4.1.

Your tests are still failing with this version. Compare changes