Whatever it was, once Core updated from 10.2.0 to 10.2.1 I no longer had the problem updating to Stage_File_Proxy 2.1.3
So you may want to close the issue as long as there is a warning by the original issue notice of the 10.2.0 to 2.1.3 bump.
Thanks
I am wondering if the issue might be the same as the one reported here:
https://www.drupal.org/project/tome/issues/3406138 🐛 The 'core_version_requirement' constraint (^9 || ^10) requires the 'core' key not be set Needs review
As I had indicated it seemed like a conflicting key type error was behind what I was experiencing.
Please consider rolling back the recommended version to 1.11 until this issue is dealt with. That build is the only one that you can simply run directly in a Composer install without crashing and burning. Unless a user is willing to go down in and edit YML file for the info on this module they will be very frustrated trying it out. It is a really valuable tool and even important to the low end user starting out with Drupal. I just hate to see users potentially being disenfranchised by this temporary hiccup.
emofsnead → created an issue.
hestenet → credited emofsnead → .
emofsnead → made their first commit to this issue’s fork.