Update composer.json
1 unresolved thread
1 unresolved thread
Related to #3112055
Merge request reports
Activity
28 28 }, 29 29 "patches": { 30 30 "drupal/core": { 31 "2869592 - Disabled update module shouldn't produce a status report warning": "https://www.drupal.org/files/issues/2869592-remove-update-warning-7.patch" 31 "2869592 - Disabled update module shouldn't produce a status report warning": "https://git.drupalcode.org/project/drupal/-/merge_requests/1517.diff" This seems to take the direct MR diff as the change instead of a static file. This is generally a bad practise as noted in https://docs.cweagans.net/composer-patches/usage/defining-patches: The contents of these patches can change by pushing more commits to a pull request or merge request. A malicious user could abuse this behavior to cause you to deploy code that you didn’t mean to deploy. If you must use a PR/MR as the basis for a patch, download the patch, include it in your project, and apply the patch using the local path instead.
Please register or sign in to reply