@naveenvalecha

Here's the patch against the 8.x-3.7 version
The PR is opened for review

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

The PR is outdated and module is already compatible with Drupal 10 and using sendgrid_api 2.0 version of the module https://git.drupalcode.org/project/sendgrid_mailer/-/blob/1.1.x/composer...
Closing this issue as outdated.

Here's a blog post https://www.morpht.com/blog/unleashing-power-metatag-custom-tags which would help you.
I'll write a drupal org handbook page for custom tags

I have opened the PR with the fix.
We need tests which I'll add later

naveenvalecha → created an issue.

PR has been merged to 2.1.x
It will be rolled out in next release.

This has been covered in 🐛 Field cardinality settings broken after 10.2 update Needs review

PR has been merged to 2.0.x
It will be rolled out in next release.

@naveenvalecha please let us keep working on latest MR in case anything else needs to be done.

I toggled to the other PR because this issue is targeted for the 4.2.x and the Drupal 11 support will be catered in 4.2.x See my previous comment 📌 Drupal 11 compatibility fixes for devel_entity_updates Needs work . The good thing now you have changed the target branch of MR 5 is 4.2.x which bring issue to the right direction.
Now there's no need to hide the other PR https://git.drupalcode.org/project/devel_entity_updates/-/merge_requests/4 you could close it.

Good progress during holidays. Issue is RTBC

Merge request looks good to me. However, asked few questions on the MR

Pinged @plach over slack about the Drupal core compatibility across devel_entity_updates 4.2.x version.

if 4.2.x is only for drush 13 then we need to bump core requirements to ^10.3
Please advice.

naveenvalecha → changed the visibility of the branch 3454902-drupal-11-compatibility to hidden.

naveenvalecha → changed the visibility of the branch 3454902-d11 to active.

Issue is ready for review.
cspell has been addressed as well.
There are some false positive in phpstan

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

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

@alex.skrypnyk
I have tried out placing the links--contextual.html.twig in the subtheme but that didn't work well.

I tried to accomodate another advice by placing directly in civictheme_preprocess_block__system_branding_block and that also didn't work either.

$variables['modifier_class'] = FALSE;

We're now facing this issue on a sub theme based on civictheme

I have updated the Gitlab CI template to run on the combination of matrix
Also updated the core version requirement to support the active Drupal versions.
Also fixed the cspell and PHPCS
However, the cspell job is failing for this word d'essai I have failed an issue at gitlab_templates https://www.drupal.org/project/gitlab_templates/issues/3478155 🐛 cspell job is not ignoring the word "d'essai" Active

Adding Novice tag to the issue to work on the replacement of deprecated functions with their new replacements.

naveenvalecha → created an issue.

We're using this patch on a customer website from a long time and it's working fine for us without any problem.
RTBC + 1

This has been covered in 📌 Automated Drupal 11 compatibility fixes for custom_meta Needs review

PR has been merged to 2.1.x
It will be rolled out in next release.

Enabled after https://www.drupal.org/project/metatag/releases/2.0.2 →

@greg.1.anderson Thank you!

PR has been merged to 1.0.x branch
It will be rolled out in next release.

PR rebased and its ready for review

The PR is outdated and needs update
going to do it

PR has been merged to 1.0.x
It will be rolled out in next release.

It's because the composer require command is special for this project by drupalorg.

Here's the composer command copied from the project page.

composer require 'drupal/augmentor_google_cloud_text_to_speech-augmentor_google_cloud_text_to_speech:^1.0'

Let me know if you still face any difficulty.

PR looks good to me
PR has been merged to 1.0.x
It will be rolled out in next release.

naveenvalecha → changed the visibility of the branch 3459206-drupal-11-compatibility to active.

naveenvalecha → changed the visibility of the branch 3459206-drupal-11-compatibility to hidden.

There's new stable release of encrypt module is out with Drupal 11 support https://www.drupal.org/project/encrypt/releases/8.x-3.2 →

git.drupalcode.org is a domain controlled by the infrastructure team, in the same way drupal.org is.

Updated the issue summary based on #3

naveenvalecha → created an issue. See original summary → .

The Dev branch needs to be opened to test it against the latest dev version
I have pinged maintainers @chrissnyder and @bygeoffthompson over slack for their attention on this issue

Super clean

Closing it because maintainer has dropped the support of 8.x-1.x
2.0.x branch is Drupal 11 compatible.

setting to Active so that bot post an updated PR

Closing it as duplicate of 📌 Automated Drupal 11 compatibility fixes for gtranslate Needs review

Setting it to Active so that bot should spin up a new PR

Closing as outdated because 1.2.0 is not supported anymore.

naveenvalecha → created an issue.

The Drupal 11 support has been added in 2.x branch as part of this commit https://git.drupalcode.org/project/pantheon_advanced_page_cache/-/commit...

@greg1anderson Could this issue be closed?

@grevil Thank you for your contribution in 📌 Automated Drupal 11 compatibility fixes for remove_http_headers RTBC

As per project ownership, Please update the issue https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

RTBC +1

@cmlara Thanks for spinning up the new PR.

I have closed 📌 Automated Drupal 11 compatibility fixes for tfa Needs review as duplicate
Pinged @rlhawk → , maintainer of encrypt module for rolling out a new release of encrypt.

Closing this as duplicate of ✨ Add D11 Support Active

I have closed other issue as duplicate 📌 Automated Drupal 11 compatibility fixes for unique_content_field_validation Needs review
@mably Thank you for your contribution! I have endorsed you here https://www.drupal.org/project/unique_content_field_validation/issues/34... ✨ Offering to maintain Unique content field validation Active for a co-maintainer.

Unassigning it from you so that it's open for the community to provide review & feedback on it.

+1 to @mably as a co-maintainer based on his contribution in ✨ Drupal 11 compatibility fixes for Unique content field validation Active

Closing it as duplicate of ✨ Drupal 11 compatibility fixes for Unique content field validation Active

Closing it as duplicate of 📌 Automated Drupal 11 compatibility fixes for unique_content_field_validation Needs review

The MR is ready for review

Assigning to eleo for review

Mark this module as deprecated in 1.2.x release by doing the following
Add lifeycle and lifecycle_link attribute in modules/augmentor_ckeditor4/augmentor_ckeditor4.info.yml

lifecycle: deprecated
lifecycle_link: https://www.drupal.org/project/augmentor/issues/3469771

Remove it in next 1.3.x release

---

We can't remove it in next minor stable release.

I can confirm that #32 works.
It failed our nightly job on Drupal core 10.3.5 https://github.com/morpht/convivial/actions/runs/11003139985/job/3055159...

  +-------------------+----------------------------------------------------------------------------------+
  | Package           | drupal/core                                                                      |
  | CVE               | CVE-2024-45440                                                                   |
  | Title             | Drupal Full Path Disclosure                                                      |
  | URL               | https://github.com/advisories/GHSA-mg8j-w93w-xjgc                                |
  | Affected versions | >=8.0.0,<=11.0.4                                                                 |
  | Reported at       | 2024-08-29T12:31:05+00:00                                                        |
  +-------------------+----------------------------------------------------------------------------------+
  +-------------------+----------------------------------------------------------------------------------+
  | Package           | drupal/core-recommended                                                          |
  | CVE               | CVE-2024-45440                                                                   |
  | Title             | Drupal Full Path Disclosure                                                      |
  | URL               | https://github.com/advisories/GHSA-mg8j-w93w-xjgc                                |
  | Affected versions | >=8.0.0,<=11.0.4                                                                 |
  | Reported at       | 2024-08-29T12:31:05+00:00                                                        |
  +-------------------+----------------------------------------------------------------------------------+
  
  The new audit.abandoned setting (currently defaulting to "report" will default to "fail" in Composer 2.7, make sure to set it to "report" or "ignore" explicitly by then if you do not want this.
  Found 2 security vulnerability advisories affecting 2 packages:
  To skip commit checks, add -n or --no-verify flag to commit command

We're using this patch on our website and it fixed the issue

Thank you everyone!
I have closed the another sibling issue as outdated 💬 Offering to co-maintain AdobeAnalytics Active

Closing this as outdated now
This project got a new co-maintainer in 💬 Offering to maintain AdobeAnalytics Fixed

Here's the patch rerolled based on #19 for Drupal core 10.3.5 site
Attaching it here if anyone needs it

Here's the patch for drupal core 10.3.5 which we're using on one of our website

@joseph.olstad

you need to wait for atleast 15 days before moving the issue to the Drupal.org project ownership project. See the guidelines

https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

+1 to add @joseh.olstad as a co-maintainer
I don't have rights to add you as a co-maintainer

The PR is opened for review

@damienmckenna
Thanks for the update on the 2.1.x branch here https://www.drupal.org/project/metatag/issues/3423884#comment-15770300 🌱 Plan for Metatag 2.1.0 Active
I don't have the capability to change the target branch of the PR from 2.0.x to 2.1.x https://git.drupalcode.org/project/metatag/-/merge_requests/94
Could you do that and then I'll update the PR OR should I open a new PR?
Please advice.

#8 Great news!
Updating the version

Adding a Novice tag for the quick change requested in #note-12

naveenvalecha → created an issue.

PR has been merged to 1.1.x
It will be rolled out in next release.

PR has been merged to 1.2.x

Unpostponing it after 📌 Automated Drupal 11 compatibility fixes for paragraphs Needs review

Opened a new PR against 1.2.x

The fix has been committed to 2.0.x
it will be rolled out it in next release.

naveenvalecha → created an issue.

PR has been merged to 1.0.x
It will be rolled out in next release.

PR is ready for review

MR is ready for review

naveenvalecha → created an issue.

naveenvalecha → created an issue.

The fix is ready for review

naveenvalecha → created an issue.

@chris matthews
Thank you for committing it and rolling out a new release Drupal 11 compatible release https://www.drupal.org/project/sendgrid_integration/releases/8.x-2.3 →

naveenvalecha → created an issue.

Merging PR

Thank you for the contribution
PR has been merged to 2.0.x
It will be rolled out in next release.