Version 2.1.3 Update conflict with Core 10.2.0 update

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.

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 just compared version 2.1.3 with the previous 2.1.2. The line that causes the issue is

https://git.drupalcode.org/project/stage_file_proxy/-/compare/2.1.2...2....

If I revert that to what it was before, it works again. I created a patch for that for the meantime.

🐛 CORS headers aren't applied to the module response Fixed is the issue in question.

Does a fresh install cause the issue?

May have saw this issue in the pipeline and it had to do with the drush version https://git.drupalcode.org/project/stage_file_proxy/-/jobs/680142

Which I upped in https://git.drupalcode.org/project/stage_file_proxy/-/commit/61b04be0fb3...

Did that resolve it?

Added a reference to https://www.drupal.org/project/stage_file_proxy/issues/3417922 📌 Drush 12 compatibility Active in order to handle a drush 12 compatibility

If drush is indeed the issue then this can be closed.

Going to close this out as assuming drush was the issue. Merged the related issue.