Cannot apply patch 2869592 with 10.3.x

Also, I will request that if someone can help to fix this issue: https://www.drupal.org/project/lightning_core/issues/3456184 🐛 AssertionError: assert($typed_config instanceof Mapping) in assert() Active with same version and facilitate it's fix release with this same upcoming release then will be best help.

smitghelani → closed merge request !35

Open MR is already there with same fix : https://git.drupalcode.org/project/lightning_core/-/merge_requests/33
please review and merge it to get this issue fixed.

i have the same issue

I have the same issue. Unfortunately lightning is still so tightly interwoven with my site that I haven't been able to fully divest it. Now this patch from a module (ugh!) won't apply.

There is another issue dealing with this. This one should be closed. But the code to ignore the patch from #6 in that thread worked for me:

 "enable-patching": true,
        "patches-ignore": {
          "drupal/lightning_core": {
            "drupal/core": {
              "2869592 - Disabled update module shouldn't produce a status report warning": "https://www.drupal.org/files/issues/2869592-remove-update-warning-7.patch"
            }
          }
        },
        "patches": {

Thankssssssssssssssss it`ssss workssssssssssss

Seems its not working with Drupal 10.3.5
Anyone tired with this version?

Still encountering issues upgrading to 10.3.0 I just created a patch to remove it from the composer.json of lightning_core

another temporary workaround to fix the problem for 10.3
instead remove or ignore old patch I added small core patch to let '2869592-remove-update-warning-7.patch' patch work :-)

Facing the same issue while upgrading to 10.3.6. Tried applying the lightning_core-remove-not-applicaple-patch.patch → but it's not working for me. Any suggestions?

I can confirm with @robbdavis (#11) that the course of action to circumvent this issue is to apply the code in #6. This allowed us to update a site from D10.2.6 to 10.3.10.