An in-range update of fullcalendar is breaking the build 🚨

[greenkeeper]

Version 3.3.0 of fullcalendar just got published.

Branch	Build failing 🚨
Dependency	fullcalendar
Current Version	3.2.0
Type	dependency

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

As fullcalendar 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 could not complete due to an error Details

Commits

The new version differs by 121 commits (ahead by 121, behind by 1).

• cdbc0bf version 3.3.0
• 3ac1ea7 changelog date
• 403d4ca test stub
• f3fff0b more tests about mutation
• fb54981 visibleRange should receive zoned date
• 3ca5696 test for dynamic visibleRange
• 33209a2 changelog about generic view
• 06fdff2 updated demo dates
• dc0bbf0 problem with inverse events
• 81e21de more changelog
• e7e5a8a touch punch manual test
• b503728 tests, for repeating event bug
• 6163746 bug with out-of-range events and same-id
• ea215a7 more coords
• 91a8526 adjust how re-selections happen

There are 121 commits in total. See the full diff.

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 🌴

[ryanhugh]

Looks like this has nothing to do with fullcalendar. Looks like travis is now installing packages with yarn --frozen-lockfile (which isn't working) instead of yarn (which does work) which is causing this to crash.

[ryanhugh]

Annnnnnnnd travis went back to using yarn to install. Builds work again. o_O