🇵🇱Poland @patbsh

patbsh → created an issue.

Thank you @tirupati_singh, this is now merged and the fix will come with the next release (5.1.1).

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

patbsh → changed the visibility of the branch 3520435-pipelinest to hidden.

I changed it and it did not help, but definitely reduced the artifact size.

However I managed to fix it locally by overriding the .composer-base:artifacts:exclude section, specifically by excluding node_modules directory from web/core:

composer:
  extends: .composer-base
  variables:
    DRUPAL_CORE: "11.1.0"
  artifacts:
    exclude:
      - '.git'
      - '.git/**/*'
      - '$_WEB_ROOT/**/.git'
      - '$_WEB_ROOT/**/.git/**/*'
      - 'vendor/**/.git'
      - 'vendor/**/.git/**/*'
      - '$_WEB_ROOT/core/node_modules/**/*'
    paths:
      - .

The issue is unfortunately not resolved, we still face the same exact problem. The said module is now removed from repositories in composer.json file as the issue was fixed. There is now a new package added in repositories instead (mably/slick) but removing it does not fix the problem and the artifact is still too large so the job fails.

example build log: https://git.drupalcode.org/issue/droopler-3520435/-/jobs/5037201

patbsh → created an issue.

patbsh → created an issue.

@leducdubleuet, changed the settings and it should mark Droopler 3.3 as supported now :)

Works perfect, it was also probably due to unrun hook on my end and a build would've fixed it. Thank you for a very prompt response.

patbsh → created an issue.

patbsh → created an issue.

patbsh → created an issue.

I've checked the upgrade status and was able to meet the requirements there:

1. field_validation module is incompatible but can be removed since it is not even installed in the distribution
2. update webform to 6.3.0-beta1
3. update radix to 6.0.1
4. Advanced Link attributes -> there is no release that is d11 ready, I found this automated fix https://www.drupal.org/project/ala/issues/3428146 📌 Automated Drupal 11 compatibility fixes for ala Needs review with this patch upgrade status marks the module ready, but it will not work in composer update to d11 unfortunately
5. droopler_theme -> add version in droopler_theme.info.yml

With these changes upgrade status shows that the site is d11 ready

However during the upgrade process there are multiple composer updates that would need to be made (mostly from droptica/droopler and we can probably fix them) but without a release from Advanced Link attributes the update will not be possible to make

In the attached files you can find from composer why-not drupal/core ^11 and upgrade status

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

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

patbsh → created an issue.

patbsh → created an issue.

I can confirm the code works perfectly, as of yet it still isn't merged so I created a patch file with all due credit to https://www.drupal.org/u/mschudders →