Enabling integration tests with a PostgreSQL server led to the discovery
of the issue, which is documented at
https://github.com/getsentry/sentry-python/issues/3312.
Short version:
Previously, when packages added in `in_app_include` were installed to a
location outside of the project root directory, span from those packages
were not extended with OTel compatible source code information. Cases
include running Python from virtualenv created outside of the project
root directory or Python packages installed into the system using package
managers. This resulted in an inconsistency: spans from the same project
would be different, depending on the deployment method.
Add a patch to fix this issue as part of the update.
[skip changelog]
