- Issue created by @2dareis2do
- 🇦🇺Australia dpi Perth, Australia
There is no problem or error here.
Update to v1.2 when your set of dependencies allow it, i.e. when you upgrade to D11. Until then, run any version less.
- 🇺🇸United States scottsawyer Atlanta
I know this issue is closed, and the solution is upgrade to Drupal 11 to get the update, but that leaves some of us in a difficult situation when stuck on a supported version of Drupal 10. Media Iframe provides a vital function for our site, but we are not yet able to upgrade to Drupal 11. However, we can also not update from Drupal 10.2 to 10.4.5 with this module.
Would you be open to an MR that extends the 1.1 branch constraint to support Drupal 10.4.5?
- 🇦🇺Australia dpi Perth, Australia
. However, we can also not update from Drupal 10.2 to 10.4.5 with this module.
I dont understand how this can be true. Whats stopping you from running the version you are currently on, indefinitely?
- 🇺🇸United States scottsawyer Atlanta
Because I misread the version constraint! Sorry.
- 🇬🇧United Kingdom 2dareis2do
Thanks for your response.
Will ignore the notice for now. Just slightly annoying.
I know with Drupal, not everyone is on the latest version, i.e. 11.x. myself included.
I am sticking with 10.x for now so it is disappointing to see support being dropped with the latest 1.x version. Perhaps there is a good reason for that? Perhaps CI is only compatible with Drupal 11?
- 🇦🇺Australia dpi Perth, Australia
it is disappointing to see support being dropped with the latest 1.x version
Just like core, time is focused on the single main branch. for contrib, time is already spread so thin.
If there is a critical bug fix or security issue, it will be backported.
But you won't get anything new from this project.
But also, this project is largely "complete", so there is not much to miss out on.
