Plan for Panels 8.x-4.8 release

Would be great to include 📌 Change ctools dependency from ^3.12 to ^3.12 || ^4.0 to allow for a smooth upgrade process Fixed

This issue is six years old, indicating its significant age.
Upon closer inspection, I realized that I hadn't noticed it initially. It would be beneficial if Drupal.org issues could be pinned.

Proposed resolution

• Release the 8.x-4.8 tag to allow for more testing on install and update.
• Have the full check and support for PHP 8.2 in a new issue.
• Not to be blocked with 📌 Change ctools dependency from ^3.12 to ^3.12 || ^4.0 to allow for a smooth upgrade process Fixed
• Implementing micro releases and micro deployments helps to minimize issues.

🌱 Release Panels 4.8.0 or a new 5.0.x branch and 5.0.0-alpha1 tag Closed: duplicate
Feel free to close the issue if it was not inline with the plan.

I think we should close either this issue or https://www.drupal.org/project/panels/issues/3359684 🌱 Release Panels 4.8.0 or a new 5.0.x branch and 5.0.0-alpha1 tag Closed: duplicate

they seem like duplicates to me

thanks for your work on this @Rajab Natshah.

Would any maintainers care to chime in on this? The ctools and jquery_ui dependency issues (the later of which is fixed in dev, I believe) are blockers for some of us who'd like to be on the latest versions. While this module is not being actively developed for new features, I think these issues squarely fall within the realm of "maintaining current functionality and compatibility". As such, I'd love to see a new release with these fixes. I'd appreciate maintainer feedback and am happy to assist.

looks like we are close just have these left:

🐛 Update test coverage for "Form error messages do not appear in IPE" Closed: outdated
#2854542: PanelsIPEBlockPluginForm should use a real submit function →
#2856475: Allow Panels Display UUID to change to enable Panelizer use cases →

and
🐛 Fix HEAD test failures for 4.x Needs review

this is great news! Thanks everyone for their work, I'm excited we may cross the finish line soon :)

I suggest that the current 8.x-4.x be released as 8.x-4.8 and the remaining issues be moved to 8.x-4.9. There are lots of integers, so it's not a waste to make a release and then shortly afterwards make another. There haven't been any commits since August. It would be nice to get those commits released.

There has been no development in several months on the issues identified in #12. Is there a reason we can't tag 8.x-4.8 now and move the remaining issues to 8.x-4.9?

There's two RTBC patches ready to go in that will fix the HEAD automated test failures.

🐛 Fix HEAD test failures for 4.x Needs review
AND
🐛 Load context for page that IPE is editing, rather than AJAX or form route RTBC

@joelpittet, 8.x-4.8 should include these two head test fixes
please go ahead with these!

amazing, thanks @joseph.olstad!

https://www.drupal.org/project/panels/releases/8.x-4.8-rc1 →

congrats, thanks you all for the work!

Do you know if composer handles `^4.8-rc1` gracefully, such that future 4.8 rcs and 4.8.1 or 4.9.0 would be accepted when available?

If you put "drupal/panels": "^4.8" in your composer.json, it should pull in the RC.

amazing, thank you for the clarification, very much appreciated

This should work:

composer require 'drupal/panels:^4.8@RC'

I'd stick to this ^ just in case. It should work fine on future rc releases and future minors.

awesome, thanks!

Which you choose depends on whether you want to get every RC or just this one.

https://www.drupal.org/project/panels/releases/8.x-4.8 →

Automatically closed - issue fixed for 2 weeks with no activity.