@Ligonsker so you can't run composer locally? Why? And do you get this error on your local environment or production? You removed the bootstrap/cache folder locally or on production? Too many unknowns.
These kind of issues are extremely hard do track down for several reasons, but the biggest one is that this code exists in the vendor directory, which means that you need to get down and dirty into the inner workings of Laraval, and that my friend requires a shit load of time spent source diving.
I think you should buy the Security guys some lunch so that the will allow you to use Laravel Shift.
@Tray2 🤣🤣😂if that'd work then definitely. But it's not even related to the upgrade yet! I'm just afraid of what's to come when we start to (try) upgrade