Problem/Motivation

There have been a couple of dependency updates since #3176504: Upgrade dependencies prior to 9.1.0 - let's update before the alpha.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

+-------------------------------+--------+--------+
| Production Changes            | From   | To     |
+-------------------------------+--------+--------+
| symfony/http-client-contracts | v2.2.0 | v2.3.1 |
+-------------------------------+--------+--------+

+-------------------+---------+---------+
| Dev Changes       | From    | To      |
+-------------------+---------+---------+
| composer/composer | 1.10.14 | 1.10.15 |
+-------------------+---------+---------+
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

alexpott created an issue. See original summary.

alexpott’s picture

Issue summary: View changes
Priority: Normal » Critical
Status: Active » Needs review
FileSize
4.38 KB
alexpott’s picture

I've made this critical due to...

+++ b/composer.lock
@@ -7324,5 +7325,5 @@
-    "plugin-api-version": "2.0.0"
+    "plugin-api-version": "1.1.0"

Composer 2 seeping into core composer config...

xjm’s picture

Priority: Critical » Major

So far #3 has not had any negative effects reported (we tested it with 9.07 and 8.9.7 on purpose). AFAIK it will get changed depending on the Composer version used by the person who most recently did a Composer update of core (most often the release managers).

alexpott’s picture

EDIT: duplicate of previous comment

xjm’s picture

Note that we need a separate 9.1.x patch; post-8.8.0 different branches will always have mismatched lockfiles.

alexpott’s picture

Here's a patch for 9.1.x. Amusingly the conflict is on the diff in #3 - also the composer bin thing is flipping again.

jungle’s picture

#7 for 9.1.x looks good to me.
#2 for 9.2.x, I think we could stick with "plugin-api-version": "2.0.0" to inline with 9.1.x switching to composer 2, otherwise, it's RTBC to me.

Thanks!

jungle’s picture

In addition to #8, should/could we upgrade PHPUnit to 9 in 9.2.x?

jungle’s picture

Status: Needs review » Reviewed & tested by the community

As the title indicated, it's for 9.1.x. so setting to RTBC.

jungle’s picture

Status: Reviewed & tested by the community » Needs review

I got confused that in composer.lock, it's "plugin-api-version": "1.1.0". See https://git.drupalcode.org/project/drupal/-/blob/9.1.x/composer.lock#L7327. Changing back to NR

alexpott’s picture

@jungle the plugin-api-version doesn't matter. It only records what version of composer was used to do the build. It'll flip-flop. We shouldn't be committing composer.lock at all.

alexpott’s picture

See https://github.com/composer/composer/search?q=plugin-api-version - it's not actually used by composer and is not even part of the lock file hash :)

alexpott’s picture

Re #9 no - that's optional. We need to stay on PHPUnit 8 whilst we still support it so we run tests with it. As said before we shouldn't check in composer.lock but we should do min-max testing instead.

andypost’s picture

Status: Needs review » Reviewed & tested by the community

+1 rtbc

  • catch committed 066f155 on 9.2.x
    Issue #3178046 by alexpott, jungle, xjm: Update dependencies for 9.1.x
    

  • catch committed 0b9b8e6 on 9.1.x
    Issue #3178046 by alexpott, jungle, xjm: Update dependencies for 9.1.x
    
catch’s picture

Status: Reviewed & tested by the community » Fixed

Committed the patches to 9.2.x and 9.1.x respectively, thanks!

jungle’s picture

See https://github.com/composer/composer/search?q=plugin-api-version - it's not actually used by composer and is not even part of the lock file hash :)

@alexpott, thanks for the clarification.

xjm’s picture

Issue tags: +9.1.0 release notes

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.