#ProjectUpdateBotD11

Is there going to be a 3.0.x tagged release for tablefield?

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

Thanks, Max! Yes, we use this at UT Austin. A representative implementation: https://cml.music.utexas.edu/about/video-essays-learning-music

rahul17 → changed the visibility of the branch 3430234-d11_ready to hidden.

@grevil, not sure which of your MR is the one you're woking on but I think you should keep the change I made to ReportsListBuilder.php in the MR#18. See #3342975 📌 Deprecate Url::toRenderArray() and Url::renderAccess() Fixed + #3406432 📌 Remove calls of deprecated toRenderArray() method Fixed .

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

Verified MR !7 in Drupal 10 and Drupal 11, it makes module compatible with Drupal 11 and functionality is working fine.

Moving this to RTBC.

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

The leaflet_more_markers 1.1.3 release has been tested on a live Drupal 11 instance and the module works as designed.

Thank you to @itamair for committing this D11 compatible version.

antonnavi → closed merge request !2

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

nicolasgraph → closed merge request !18

#MR22 works with D10 and D11.

MR!9 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

Hi,

+1 for a merge and a D11 compatibility release.

Hi,

+1 for a merge and new release for D11 compatibility.

Thanks all for the contribution, I have made a few tricks, so the module still works on Drupal 9.3 and above.

I tested it on Drupal 10 and 11, works like a charm

Looks good to me!

#MR 8 works with vanilla D10 and also with D11.

Verified MR !43 in Drupal 10 and Drupal 11, functionality is working fine and module is compatible with Drupal 11.

ivnish → closed merge request !16

Thanks for this!!

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

Thank you Mark. I'll see what I can do this week. The changes look appropriate. Thank you for working through a manual test of the functionality as well. It seems to be all well and good on my local D11 too.

Are you using this at UT Austin?

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

I confirm the issue mentioned by @vesnag at #7

I've created a new MR requering a maxlength ^3.1 which is compatible with D10 and solves the issue for me by using composer aliases.

However, I noticed we have another issue but with the registration_role module which doesn't have a public release compatible with D11. Still, it seems they it almost ready per 🐛 Drupal 11 - Update Code - Needs review and the oly thing pending is ti publish a new release. We need to wait I think.

Meanwhile we address both, these issues can be fixed on you projects by using composer aliases (https://getcomposer.org/doc/articles/aliases.md) like

"drupal/maxlength": "3.1.0 as 2.1.3",
"drupal/registration_role": "2.x-dev as 2.0.1"

Thanks for this awesome project!

Progress?

Would be great to have a Drupal 11 version that composer can install.

Thanks for checking! Maybe you can add it to the issue patch? I guess it's 3450990-automated-drupal-11 since it says "Warning: The 'project-update-bot-only' branch will always be overwritten. Do not work in that branch!"

You may need to click "Get push access" first.

djdevin → closed merge request !2

djdevin → closed merge request !3

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

I just ran a super simple test with Article and it worked fine. No errors or warnings in the log.

I was able to enable the module. But I'll have to do some more testing to see if it actually works!

@luksak The update was merged a while ago, and I just cut release 8.x-1.4, so we should be good to go.

I didn't cut a release initially because there might be a conflict with Twig dependencies. This module uses ajgl/breakpoint-twig-extension 0.3.4:

https://git.drupalcode.org/project/twig_xdebug/-/blob/8.x-1.x/composer.j...

Which doesn't support Twig 3 (which Drupal 11 uses). But, 0.3.5 does, so we should be good to go.

https://packagist.org/packages/ajgl/breakpoint-twig-extension#0.3.4
https://packagist.org/packages/ajgl/breakpoint-twig-extension#0.3.5

At some point we should update to 0.4 version of ajgl/breakpoint-twig-extension, but I don't know what work that will require.

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

It's compatible with Drupal 11 now.

I applied the patch on a site running 10.3 and checked the module's Drupal 11 compatibility using upgrade status module (static analysis). Functionally, the module works the same.

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

I am fairly sure the test failures are unrelated, but I can't prove it. So back to NW because of the test failures.

grevil → changed the visibility of the branch 3428485-TESTS-WILL-FAIL to hidden.

Hi maintainers - When will you make a Drupal 11 release of this module?

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

vipin.j → made their first commit to this issue’s fork.

Adjusted accordingly @zaporylie, let's see if the tests succeed.

@fgm sorry, stack overflow in my brain ;D Yes!

Would be great to get a D11-compatible release!

I got confused because the most updated branch was project-update-bot-only and the MR was oldest. I hid the outdated branch (opposite of what I did before).

The branch now has no deprecations running phpunit. There still one risky test but I think that is out of scope of this issue.

Glad to see one of the maintainers around :)

The MR is ready to review again

rodrigoaguilera → changed the visibility of the branch 3434446-automated-drupal-11 to hidden.

rodrigoaguilera → changed the visibility of the branch project-update-bot-only to active.

Looks good to me.
Hopefully a new D11-compatible release can be tagged soon by the maintainers.

Can a new release be created for Drupal 11, so we do not have to rely on the lenient Composer endpoint?
Especially given D11 support does not require any code changes, other than tagging the module as D11 compatible.

Reviewed the MR and this seems to work as intended for Drupal 11.
Can this be merged in and a new release created with Drupal 11 support, given Drupal 11 has been released for a while now?

I fixed the deprecations but now there is some tests failures. Need a deeper look. I can't right now

@anybody: seems your sentence is missing a word ? Maybe it was "mark" ?

All other issues are blocked by this one as tests are currently failing against D11. I left a comment on the MR (requested feedback).

Cool! I'm a maintainer now. Let's fix this module together :)

Good catch.
Let me have a look

rodrigoaguilera → changed the visibility of the branch project-update-bot-only to hidden.

Guess we can now that this fixed?

https://git.drupalcode.org/issue/select_or_other-3434446/-/jobs/3062446

Some tests has deprecations. I think needs to investigate and fix it

Same here. Looks good to me.

oscarnovasf → closed merge request !2

Thanks!

Done.

We're changing the services.yml - don't we need to clear the container cache @grevil?

Last time I checked this, clearing the container cache did not make a difference, but yea, I can add that.

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

MR!7 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

New release and instructions for those still using D10.2.

https://www.drupal.org/project/bootstrap/releases/8.x-3.34 →

Hi @danchadwick , thanks for reporting this issue.

According to this report, it means that anyone using 10.2 will want to stick to 3.32 instead of upgrading.

Thank you for your contributions. Merged to 2.x :)

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

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

m.abdulqader → credited omar_emailat → .

Noting support for Drupal 11, dropping support for Drupal 8, closing this as Drupal 11 is out and this module supports it.

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

google_tag module has a release compatible with D11, but this release has some issues. Therefore none of these two modules works correctly on D11. I have pinged @japerry on Slack (he is the maintainer of both modules).

I notified maintainer in slack https://drupal.slack.com/archives/C1BMUQ9U6/p1733047217992269

I have created a new MR !9, where I have put together a fix from the project update bot, 🐛 user_roles() is Deprecated Needs review and updated the .info file to support D11.

I noticed that MR created for 8.x branch. This branch is not in development yet.

ivnish → changed the visibility of the branch support-gitlabci to hidden.

ivnish → changed the visibility of the branch 3455277-automated-drupal-11 to hidden.

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

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

I have created a new MR !30 and moved here (hopefully) all required changes (this includes the changes from project update bot, 🐛 The spaceless tag was removed in Twig Active , EntityReferenceTestTrait deprecation and toRenderArray deprecation). Given the EntityReferenceTestTrait deprecation, I had to remove compatibility for Drupal 10.1 and lower (unless we want to add some exceptions/special checks), so I think that this probably should go to a new branch, instead of 8.x-1.x.

@valic It would be great if you can tag a D11 compatible release, ideally with Commerce 3 support (there is another issue open for this). Thanks!

This issue requires D10.2, but its 10.3 that has the stick table header change that this issue requires. Not sure if the issue status should be changed to needs work or what.

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

Here is the new release: https://www.drupal.org/project/xmlsitemap/releases/2.0.0-beta1 →

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

Merged this to 2.x, thanks everyone! Closing this as fixed - if there will be any other issues, please open a new issue. 8.x-1.x will remain without the D11 support, as that is much easier. And I will create a new 2.0.0-beta1 release today.

Yeah! Thank you, @poker10

Saving credits.

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

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

Already done on 2.0.x. We will publish a new official release on 2.0.x branch.

I also add composer.json update. Thanks to everyone. I close the issue as Done.

It is already merged into develop. I close the issues as Done.

Giving credit, thanks for the reminder!

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

Thanks, I think that's what I tried, but I still got an error in Drupal 11 ... Or does it work in Drupal 11 for you?

Looks like nice work and thanks! Please let me know if there's an issue with this release that relates to these changes.

heddn → closed merge request !2

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

That was quick, thanks @nginex!

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

D11 support has been added to new release 2.1.2

I leave the issue open for new updates by the bot

Tested the example payment form and all seemed to work successfully.

steffenr → closed merge request !22

Thanks for your contributions.

Like so?

Need maintainer feedback on https://git.drupalcode.org/project/commerce_reports/-/merge_requests/20#....

Nice @maintainers could you maybe create a 3.x branch to comply with commerce 3.x? Thanks!

There were a couple of issues with the original branch, I created a new one, with the D11 changes.

grevil → changed the visibility of the branch 3428485-manual-drupal-11 to hidden.

grevil → changed the visibility of the branch project-update-bot-only to hidden.

og is only a dev dependency so setting it to ^1.x-dev for now.

embed.module support for D11 got rolled back. We'll need to wait on https://www.drupal.org/project/embed/issues/3430097 📌 Automated Drupal 11 compatibility fixes for embed Needs work to land first. I'm way down the line in https://www.drupal.org/project/media_migration/issues/3431903 📌 Automated Drupal 11 compatibility fixes for media_migration Needs review waiting for this to land. So hopefully the upstream issues land soonish.

MR!7 Makes this module compatible with Drupal 11. Functionality is working as expected.

changes in MR !6 is working fine in Drupal 10 and Drupal 11.

RTBC +1

+1 for Drupal 11 release. It seems that this MR fixes BC and the 2.0.x-dev branch is already Drupal 11 compatible. Are there any other blockers?

What's the status here can we get this commited?

Yeah! Thank you!

Merged. Leaving open for more automated patches.

Sending a message to Colan today

Tests are back to failing again.

https://www.drupal.org/project/fast_404/releases/8.x-3.4 →

Can this be checked, merged, and released? This is one of the last modules blocking us from updating a couple of sites to D11!

MR!39 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

I functionally tested this module in the context of Drupal 11 and can confirm that the basic functionality -- that of using AblePlayer's field formatter -- works as expected. As such, I'm marking this as RTBC.

Static analysis of the code did not turn up any Drupal 11 deprecations, per se, but there was missing schema definitions, and outdated implementations in the tests. I updated those where I could -- it's clear that one of the tests is a work-in-progress, so I let that be -- and now PHPUnit tests are passing on both Drupal 10 and Drupal 11.

Of note: the maintainers have set the minimum core version requirement to ^10.3 in the 3.x development branch. Based on my reading of the latest views in https://www.drupal.org/project/ideas/issues/3357742 🌱 Guidelines for semantic versioning and Drupal core support Needs review , this module can drop support for Drupal 9 in a minor version release, since Drupal 9 is no longer supported.

I therefore encourage the maintainers to release a 3.2.0 minor version release that provides Drupal 11 compatibility, given that Drupal 11 has been released for nearly six months now. Thank you!

Tested in Drupal 10.3.10 and 11.0.9. Setting to RTBC.

Thanks to everyone involved in making this happen, especially to joseph.olstad for pushing the work :)

Verified functionality in Drupal 10 and Drupal 11 which is working fine and module is Drupal 11 compatible.
Moving this to RTBC.

Published 8.x-3.33 →