Stefano Arlandini

I'm putting this on the backlog because I know that the DX on Laravel is far better than our, so it makes sense for me to keep track of this...

>Is this intended behaviour? To be honest, I think we didn't think about this behaviour at all. What's happening is that since the `sentry.options.release` default value is taken from `PrettyVersions::getRootPackageVersion()->getPrettyVersion()`,...

@kamilogorek do you think that it would make sense to prefer the environment variable to the version stored in the `composer.json`? I think that the same question may apply on...

ODM support is not built-in into this SDK yet. It's definitely something that we may want to introduce, but I would rather see first if there are enough people asking...

The afromentioned deprecations about the `HubAdapter` class have been solved with the `3.2.2` version of the core SDK. The first one instead is not an easy task as of now...

I bet it won't, but can you please try updating to `4.2.3` and see if it solves the problem?

I think that the deprecation gone because you also upgraded the `doctrine/dbal` package to `3.x`, otherwise it doesn't make sense because we're still implementing the old interface

I just checked some projects I work on and I definitely still see the deprecation about the `ExceptionConverterDriver` interface. Unfortunately, the issue is not that easy to solve because we...

>The deprecation warnings make it almost impossible to see real errors. I don't think that this is a fair statement. Just one deprecation remains, which is the one related to...

Please open a separate issue and post more details. An image of an error message is not enough to understand what's happening