Update Composer dependencies for 11.1.0-RC1

spokje → changed the visibility of the branch 3490163-update-composer-dependencies to hidden.

$ composer-lock-diff --no-links
+-------------------------+------------+------------+
| Production Changes      | From       | To         |
+-------------------------+------------+------------+
| pear/pear-core-minimal  | v1.10.15   | v1.10.16   |
| php-tuf/composer-stager | v2.0.0-rc5 | v2.0.0-rc6 |
+-------------------------+------------+------------+

+------------------------------+---------+---------+
| Dev Changes                  | From    | To      |
+------------------------------+---------+---------+
| composer/class-map-generator | 1.4.0   | 1.5.0   |
| composer/composer            | 2.8.2   | 2.8.3   |
| composer/pcre                | 3.3.1   | 3.3.2   |
| php-http/guzzle7-adapter     | 1.0.0   | 1.1.0   |
| phpstan/phpstan              | 1.12.10 | 1.12.11 |
| phpstan/phpstan-phpunit      | 1.4.0   | 1.4.1   |
| squizlabs/php_codesniffer    | 3.10.3  | 3.11.1  |
+------------------------------+---------+---------+

Same as the 10.5 believe this is good. Didn't notice any issues locally.

Dependency php-tuf/composer-stager with stability RC does not meet minimum stability stable.

Unsure if this dependency is allowed to be RC, or flew in under the radar when MINIMUM_STABILITY was lowered to accommodate SF.
Otherwise things look fine.

spokje → changed the visibility of the branch 11.x to hidden.

The php-tuf/composer-stager is an experimental module's dependency so should not block release

We can keep minimum stability as rc in this issue but we should open an explicit tracking issue for php-tuf to get to a stable release.

Another possibility might be to move the library to a dev dependency until package_manager is beta, but that might break package_manager tests so could be more trouble than it's worth.

spokje → changed the visibility of the branch 3490183-update-composer-dependencies to hidden.

$ git checkout -b '3490163-11.x-bump-composer-dependencies' --track drupal-3490163/'3490163-11.x-bump-composer-dependencies'
error: invalid path 'core/modules/system/tests/modules/icon_test/icons/name_special_chars/FoO !?1:èç 2 "#3 B*;**a,ù$R|~¹&{[].svg'

Well that's me on a Windows git-bash based system out of the running for core work...

I've added the tracking issue, somebody needs to pick this up and/or also my JS-dependency updates.

Unless we relax this in ComposerProjectTemplatesTest we won't be able to have tests passing on 11.1.0:

    $this->assertGreaterThanOrEqual(array_search($this->getCoreStability(), static::STABILITY_ORDER), array_search(static::MINIMUM_STABILITY, static::STABILITY_ORDER));

This prevents us from releasing a stable version of core with RC dependencies, or an RC with beta dependencies, etc.

Re #16 I reposted that in ✨ Add an icon management API Active , hopefully we can do a quick fix or just remove it for now.

Changed minimum stability back to RC.

Rebased, reverted to php-tuf/composer-stager:v2.0.0-rc5 as 2 tests failing reproducible and update coder to 8.3.26 →

on second time package manager's build tests passed with rc5

And it passed on PHP 8.4

So reverted back to latest as it was test flux

This week is enough updates for release

Committed fc9c4c2 and pushed to 11.x. Thanks!

Committed bd2b1c3 and pushed to 11.1.x. Thanks!

longwave → closed merge request !10357

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