New version of react-rails (2.6.0) broke the build

[depfu]

We've tested your project with an updated dependency and the build failed.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
react-rails	>= 1.0	2.6.0

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of react-rails for this test run.

What changed?

✳️ react-rails (>= 1.0 → 2.6.0) · Repo · Changelog

Release Notes

2.6.0

As always a big thank you to everyone who contributes to make the project a success!
🎉 We passed 7 million downloads of the Gem and 3 million on the NPM package. 🎉

New Features

• Typescript component generator #990

Deprecation

Bug Fixes

• assert_react_component will not pass tests where the case was different #979
• action_controller/test_case was accidentally required in dev #996

Thanks to all the wonderful people that helped.

@delkopiso
@huacnlee
@Aesthetikx
@HorizonShadow
@cprodhomme
@0xdevalias
@gasi
@hphu3

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 13 commits:

• Prep for 2.6 (#1006)
• Only include React::Rails::TestHelper in test environment (#996)
• Enhanced turbolinks support (#978)
• :memo: clarify using custom react version (#994)
• Chore/fix chromedriver again (#1004)
• Fix small typo: HRM --> HMR (#995)
• Typescript component generator (#990)
• Update README.md
• Update README.md (#983)
• Update README.md (#986)
• Keep variable name on assert_react_component props. (#979)
• Update README.md (#981)
• Update CHANGELOG.md

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #19.