[x] Are you reporting to the correct repository?
(enso is made of many specialized packages: https://github.com/laravel-enso)
[x] Did you check the documentation?
[x] Did you perform a cursory search?
Description
When we deleted our composer.lock file and ran composer install today our whole app broke because of the upgrade to laravael-enso/io to 2.2.2. When we tried to run composer update and/or install we get the latest version of this package which causes the backend of our app to break with an error persisting to the WebsocketServiceProvider.php file. For now, we have saved our composer.lock file with version 2.0.2 of laravel-enso/io which doesn't cause the app to break. How can we update our app to work and compile with the new /io package?
This is a bug.
Prerequisites
Description
When we deleted our composer.lock file and ran composer install today our whole app broke because of the upgrade to laravael-enso/io to 2.2.2. When we tried to run composer update and/or install we get the latest version of this package which causes the backend of our app to break with an error persisting to the WebsocketServiceProvider.php file. For now, we have saved our composer.lock file with version 2.0.2 of laravel-enso/io which doesn't cause the app to break. How can we update our app to work and compile with the new /io package?