Replies: 1 comment 1 reply
-
Hi @kingIZZZY , Laravel generally waits for stable releases of Symfony before officially supporting them. It's the same in Hypervel, we will begin the integration after the official release (maybe at the RC stage) of Hyperf 3.2. Before that, there are still other plans for us to work on on the roadmap. Due to the maintenance capacity, we need to prioritize these todos. This balanced approach allows us to maintain stability while preparing for future compatibility. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Other projects like
friendsofhyperf
are creating branches to support the upcoming Hyperf version 3.2 - example friendsofhyperf/tinker 3.2I forked almost all
hypervel
dependencies myself to achieve this effect: https://github.com/kingIZZZY/hypervel/blob/main/composer.jsonIt would be great if this could be supported in preview/development/branch in the Hypervel project as well 🙏 even before Hyperf 3.2 is released, for testing and development purposes.
Can we please start a branch to begin testing support for Hyperf 3.2 even before they release?
Beta Was this translation helpful? Give feedback.
All reactions