chore: create new jobs for React next

[nickmccurdy]

What:

• Tests with both React stable and next for all builds (push and cron)
• Allow next releases to fail the build so we can still release
• Solves cron issues like Fix build for React next #726 that are only caused by next releases

Why: #726 and greater visibility of what's failing in React next (before a cron build is started on schedule)

How: Split React next into a new section of the build matrix rather than just using it in cron builds

Checklist:

• Documentation added to the
  docs site N/A
• Tests
• Typescript definitions updated N/A
• Ready to be merged
  

[kentcdodds]

Neat!

[codecov]

Codecov Report

Merging #728 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #728   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines          100       100           
  Branches        16        16           
=========================================
  Hits           100       100           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 386c64e...a7297b3. Read the comment docs.

[nickmccurdy]

https://travis-ci.org/github/testing-library/react-testing-library/builds/704028047

Seems to be working, do we want to merge this and wait for the next cron build on master?

[eps1lon]

It doesn't really fix #726. The build still fails for react@next. We're just ignoring it because it's not as sever if it fails for experimental builds. We should still investigate if the issue is on our side or React's.

[nickmccurdy]

I see what you mean. This technically does fix the overall build though, which is what the issue was originally for. Do you want to rename it or open another issue for the timing of React next?

[eps1lon]

This technically does fix the overall build though

As far as I can tell the test is still failing. Travis even marks the build as failed. This PR makes a failing build using react@next pass github checks.

[nickmccurdy]

We merged this and kept #726 open to track the specific bug with React next.

[kentcdodds]

🎉 This PR is included in version 10.4.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀