feat(integrations): Add Lilya integration

[tarsil]

Description

Add first-class Lilya framework integration with automatic ASGI instrumentation, route-based transaction names, handled HTTP exception capture, request data extraction, authenticated user propagation, and optional middleware spans.

The integration uses Lilya-native hooks only, registers the lilya extra and typing dependency, and adds generated tox/CI coverage for Lilya 0.27.0.

Validated with:

• uv run tox -e py3.14-lilya-v0.27.0
• uv run tox -e py3.14-lilya-latest
• uv run ruff check sentry_sdk/integrations/lilya.py sentry_sdk/integrations/asgi.py tests/integrations/lilya/test_lilya.py
• uv run ruff format --check sentry_sdk/integrations/lilya.py sentry_sdk/integrations/asgi.py tests/integrations/lilya/test_lilya.py

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit cc83058. Configure here.}

[tarsil]

@sl0thentr0py apologies for tagging you but I don't want this to get lost here since this is a framework that is actually being used by some financial institutions worldwide and I always workaround to make it work but it would be great if we could natively have this in sentry?

[ericapisani]

Hi @tarsil , thanks for opening a pull request with us.

The team is currently heads down on completing a couple of projects this week, so we won't be able to review this immediately. For new frameworks, we also do additional evaluations given the team will be responsible for maintaining it after its introduction to the SDK, so we need time to do that as well.

However, can you give us more context on the workarounds that you've been doing so far? We might be able to figure something out so that it makes yours/your customer's lives a bit easier with configuring Sentry and Lilya.

[tarsil]

Hi @tarsil , thanks for opening a pull request with us.

The team is currently heads down on completing a couple of projects this week, so we won't be able to review this immediately. For new frameworks, we also do additional evaluations given the team will be responsible for maintaining it after its introduction to the SDK, so we need time to do that as well.

However, can you give us more context on the workarounds that you've been doing so far? We might be able to figure something out so that it makes yours/your customer's lives a bit easier with configuring Sentry and Lilya.

Hi @ericapisani, thank you for your reply.

The project is not new, we simply didn't hype it but its used a lot and maintained by Dymmond, a UK company.

The workaround is basically see how Starlette uses it since it shares the ASGI principle and "copy" the integration to adapt to Lilya.

[ericapisani]

Hi again @tarsil ,

Thanks for taking the time to put this together — we really do appreciate the effort that went into this PR.

I've had a chance to talk it over with the team, and we've decided not to bring on Lilya as a first-class integration in Sentry's Python SDK at this time. It's less about the framework itself and more about where we are as a team: with Lilya's current download numbers, we don't think we can commit to the ongoing maintenance an official integration requires, and we'd rather not add something we can't properly support long-term.

That said, this doesn't stop the integration from existing — if you wanted to open-source a Lilya integration yourself, we'd be glad to see it, and it's the kind of thing you could share directly with the Lilya and Sentry communities.

One thing for next time: our contributing guidelines ask that changes like this start with an issue and a quick conversation with a maintainer before you dive in. It's a small step that can save you the work of building out a full PR before we've had a chance to weigh in on scope or maintenance fit.

Thanks again for the contribution — it's genuinely appreciated even though we can't take this one on.