[Bug] While upgrading Lumen 9 to 11 Suggests Incompatible Version of symfony/psr-http-message-bridge

[mwrazorpay]

Current Version

Lumen Framework: ^9.0
PHP Version: ^8.1
Database Driver & Version: MySQL 5.7

Upgrading To

Lumen Framework: ^11.2.0
PHP Version: ^8.2
Database Driver & Version: MySQL 5.7

Description

We recently upgraded laravel/lumen-framework from version 9 to 11. The upgrade went smoothly overall—except for one issue related to our logging setup.

We use a custom tracing library (based on Monolog) for advanced logging, which relies on symfony/psr-http-message-bridge. In our setup, this package is a dependency of razorpay/trace, which requires version ^7.0 of the Symfony bridge.

However, Lumen 11 suggests using version ^2.0 of symfony/psr-http-message-bridge (mentioned here ), which causes a version conflict. Moreover, Lumen 11 still relies internally on psr/http-message:^1.0, while most modern PSR-7 implementations (e.g., nyholm/psr7:^1.6) expect compatibility with later versions of the Symfony bridge.

This mismatch prevents trace logs and PSR-7 bridging features from functioning correctly after the upgrade.

Expected Behavior

The suggested version for symfony/psr-http-message-bridge in the documentation should be updated to a version compatible with modern PSR-7 implementations and Symfony components—preferably ^7.0 or at least ^3.0+.

Suggested Fixes

• Update the "Suggested Packages" section in the documentation to recommend a compatible version (e.g., ^7.0)

• Clarify Lumen’s support for PSR-7 implementations and bridging libraries

• Ensure compatibility with modern Symfony components when using Monolog or custom logging solutions

Environment

Lumen version: 11.2.0
PHP version: 8.2

Related packages:

razorpay/trace: custom-library
symfony/psr-http-message-bridge:^2.0 (suggested, causes issue)
symfony/psr-http-message-bridge:^7.0 (required)

Steps To Reproduce

• Create or upgrade a Lumen 9 project to Lumen 11
• Include a package like razorpay/trace:custom-branch which requires symfony/psr-http-message-bridge:^7.0
• Install suggested packages from the Lumen 11 documentation
• Observe that trace logging or PSR-7 bridging fails silently or throws type errors

[GrahamCampbell]

The v7 recommendation is correct. A PR would be the best resolution here.

[mwrazorpay]

Thank you for confirming that v7 is the correct recommendation. I

However, I'd like to highlight that there's a deeper technical compatibility issue that should be addressed:

1. Lumen 11 internally uses psr/http-message:^1.0
2. Modern PSR-7 implementations (like nyholm/psr7:^1.6) expect compatibility with newer versions of the Symfony bridge
3. This creates a version conflict that affects actual functionality, not just documentation

This means that even with the documentation update, users might still face compatibility issues when:

• Using modern PSR-7 implementations
• Implementing custom logging solutions with Monolog
• Using packages that require newer versions of the Symfony bridge

Would it be possible to:

1. Review Lumen's internal PSR-7 implementation compatibility
2. Consider updating the internal psr/http-message dependency to a newer version
3. Ensure compatibility with modern Symfony components

This would help prevent similar issues for other users implementing custom logging or PSR-7 bridging features.

Would you please check and give optimal solution for fixing that particular issue?

[GrahamCampbell]

v2 and v7 are basically the same package. Almost no changes, and no breaking changes.

[GrahamCampbell]

I'd personally recommend using full fat Laravel over Lumen at this point. It's more compatible, and can actually be faster in some situations.

[mwrazorpay]

Actually, I just made these changes for the upgrade mentioned below, inside the composer update. I am not getting any conflicts while updating via composer either, but the logs of my service have stopped reflecting. Could you please suggest any way through which I could identify the cause of the issue? Because to me, it seems like a library incompatibility.

Trace custom library :

Main service composer where above trace library configured :

[github-actions]

Thank you for reporting this issue!

As Laravel is an open source project, we rely on the community to help us diagnose and fix issues as it is not possible to research and fix every issue reported to us via GitHub.

If possible, please make a pull request fixing the issue you have described, along with corresponding tests. All pull requests are promptly reviewed by the Laravel team.

Thank you!

[macropay-solutions]

@mwrazorpay we are willing to help.

Could you please suggest any way through which I could identify the cause of the issue? Because to me, it seems like a library incompatibility.

You could debug step by step what is going on and when a posible exception is thrown, use debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS) to trace what happened.

Is this happening only in lumen 11 or also in lumen 10?

Update. You are using illuminate/routing in lumen not nikic/fast-route?
We can't find the razorpay repos

[macropay-solutions]

v2 and v7 are basically the same package. Almost no changes, and no breaking changes.

@GrahamCampbell

v2.3.1 and v7.3.0 are entirely different commit histories.