Laminas MVC Retiring

[nrdevau]

Context

According to this article, Laminas MVC is retiring: https://getlaminas.org/blog/2025-06-06-laminas-mvc-is-retiring.html?trk=feed_main-feed-card_feed-article-content#content-how-to-migrate-from-laminas-mvc-to-mezzio

Problem

The main concern we're wanting to address is determining what MVC solution Magento will use post PHP 8.5.

Discussion

Some chatter from the community around this include:
https://www.linkedin.com/posts/trung-luu-09833232_laminas-project-laminas-mvc-is-retiring-activity-7341755577598910464-9xNW?utm_source=share&utm_medium=member_desktop&rcm=ACoAABGf_L4BCwByTcDebozZ-AnYnf6mphezrdc
https://magentocommeng.slack.com/archives/C4YS78WE6/p1750419803549029

Whether this impact is simply finding the few uses of Laminas/Mvc classes within the app (https://github.com/search?q=repo%3Amagento%2Fmagento2+%22Laminas%5CMvc%22&type=code) (thanks @sidolov) or whether we need to rethink how all model, view and controllers (the MVC part) are built and managed is a little unclear.

The usage of Laminas/Mvc is also around the bootstrapping of the application, so definitely a place that will have large impact regardless.

This issue is meant to aid in the community driven discussions that will happen alongside (before and probably after) the internal Adobe Magento decisions.

Alternatives (already raised)

• Magento Framework implement the PSR-7, PSR-11 and PSR-15 specification
• Magento could fork and maintain Laminas/Mvc code in the meantime

Additional Thoughts

• Symfony controllers instead of Laminas ones? https://symfony.com/doc/current/controller.html
• Magento controllers are not extensions of Laminas ones, which is good. This means this issue probably won't force all future Module devs to implement some new way of building routes and so on
• Given that we have some pretty extensive testsuites built on core nowadays, we should be able to trial alternatives with confidence! (👍 for testing!)
• Would the MFTF tests need to updated (if they're currently used?)

There are definitely others better placed to direct this discussion, but hopefully this is a good starting place.

Excited to see how Adobe and the community collaborate and "think" together! :)

Cheers,
Nate

[m2-assistant]

Hi @nrdevau. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[Vinai]

The Laminas MVC framework is only used in the bootstrapping of the Setup application in the setup/ folder - the regular Magento MVC and Event implementations do not depend on Laminas.
Only five classes have a source code dependency on the laminas/laminas-mvc package:

• setup/src/Magento/Setup/Test/Unit/Mvc/Bootstrap/InitParamListenerTest.php
• setup/src/Magento/Setup/Mvc/Bootstrap/InitParamListener.php
• setup/src/Magento/Setup/Mvc/View/Http/InjectTemplateListener.php
• setup/src/Magento/Setup/Module.php
• setup/src/Magento/Setup/Application.php

Given the situation, it would be much more efficient and secure to simply remove those classes and the dependency, rather than implementing any PSR interfaces of forking the package.
It's only a couple of hundred lines of code.

The good thing is, the deprecation only has a very minor impact on Magento, and there is plenty of time to act until November.