Problem/Motivation
Steps to reproduce
composer outdated -m
Proposed resolution
Remaining tasks
composer update
composer-lock-diff --no-links
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 3439521-nr-bot.txt | 90 bytes | needs-review-queue-bot |
Issue fork drupal-3439521
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
quietone commentedComment #5
cilefen commentedShould we fast-track #3439591: Add composer dependency on ext-zlib?
Comment #6
quietone commentedThis is failing commit-code-check.sh, specifically spelling.
Comment #7
quietone commentedComment #8
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #9
quietone commentedComment #10
smustgrave commentedSince #3439525: Update composer dependencies for Drupal 11.0 was close to the same assume this is fine.
How come #3439525: Update composer dependencies for Drupal 11.0 wasn't just backported?
Comment #11
catchCommitted/pushed to 10.3.x, thanks!
We do separate MRs because there are no backportable commits between the MRs or code changes for these - it's just committing the output of a command. Also the dependencies of the two branches have diverged a lot.
Comment #13
catch