sentry-laravel will also need to be updated to incorporate these changes. Is that on your radar already?

Thinking more about this, I have two questions:

• @Jean85, why your package doesn't require the minimum version of Composer that prevents the issue, forcing this package instead to require it?
• @99linesofcode, why should we update sentry-laravel? That package depends on this one, so once we release this change the Laravel users will benefit from it in cascade

@Jean85, why your package doesn't require the minimum version of Composer that prevents the issue, forcing this package instead to require it?

I will answer myself to this question: because the issue was not with Composer itself but with your package. I misread the package name in the composer.json and thought that 2.0.4 was the version of Composer. Sorry, long day today 🤯

sentry-laravel will also need to be updated to incorporate these changes. Is that on your radar already?

Does it? I don't think it uses anything directly, it's this base SDK that does everything, so it should be fixed without further intervention.

Does it? I don't think it uses anything directly, it's this base SDK that does everything, so it should be fixed without further intervention.

Yeah my bad. I thought maybe we had to bump the sentry/sdk version but of course its version range constrained 👍

Thanks for the quick 1-2 guys!

@ste93cry could it be that we still need to tag this in order for packagist to pick up on it properly? 🎅🎄

This is not tagged yet, yes, but you can apply the same constraint to your projects as a workaround for now.

Ops you're right, I completely forgot to release it 🤦‍♂️ Done now with version 3.3.5