Stable releases for D11 support

Created on 11 December 2024, 4 months ago

Problem/Motivation

πŸ“Œ Automated Drupal 11 compatibility fixes for image_widget_crop Needs review was recently committed. Can we see about release some tagged releases please?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🌱 Plan
Status

Active

Version

3.0

Component

User interface

Created by

heddn Nicaragua

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @heddn
  • πŸ‡ΊπŸ‡ΈUnited States joegraduate Arizona, USA

    Looks like this is blocked by πŸ› Can't save image widget crop settings in Drupal 11 Active getting commited.

  • πŸ‡ΊπŸ‡ΈUnited States joegraduate Arizona, USA

    Never mind. πŸ› Can't save image widget crop settings in Drupal 11 Active is not a D11-specific issue (see closed duplicate πŸ› ImmutableConfigException Active ).

    Also, I noticed that the 3.0.0 tag was already created in this module's Git repo. A d.o. release just needs to be created for that tag.

  • πŸ‡ΊπŸ‡ΈUnited States joegraduate Arizona, USA
  • πŸ‡ΊπŸ‡ΈUnited States mark_fullmer Tucson

    Is there anything else the community can do to move forward on a Drupal 11-compatible release of this module? The work has been merged into the 3.0.x-dev branch. Thanks for this great module!

  • πŸ‡¬πŸ‡§United Kingdom rachel_norfolk UK

    Gonna contact a couple of the maintainers and see what we can rustle up..

  • πŸ‡¬πŸ‡§United Kingdom rachel_norfolk UK

    Did a little chasing and slashrsm very kindly pressed all the right buttons. Thank you Janez!

    Urgh - as I’m not a maintainer, I can’t give them the credit they deserve...

  • πŸ‡«πŸ‡·France dqd London | N.Y.C | Paris | Hamburg | Berlin

    Before adding tags read the issue tag guidelines β†’ . Do NOT use tags for adding random keywords or duplicating any other fields. Separate terms with a comma, not a space.

    #3 Also, I noticed that the 3.0.0 tag was already created in this module's Git repo... [...]

    That's because I planned a release end of last year with some more issues I planned to fix before my brother sadly died. And I was off for the time after until end of last year and beginning of this year. I am pretty sure that I would have added some more issues before a final release and would have preferred another BETA before. But if it makes people feel better with a final release tag, I am glad that you are happy for now.

    For those who have similar situations with other modules and Drupal 11 ready MR in an issue I recommend reading about how to add a MR to composer stack as temporary package source until the issue is commited.

    I would love to see some more issues worked on and I hope to see you in there in the upcoming time. Belated Happy New Year @all.

  • Status changed to Fixed about 1 month ago
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024