Problem/Motivation

Yes, there's no alpha release yet!
Yes, it's probably too early for this!
Yes, it's an ever moving target!

I'm going to do it anyway, even if it isn't committed right away.
If we hit any major issue, this way, we have time to actually think/discuss and fix them and not be pressure-hurried by a release date.
</End of smugness>

We should release 11.1.0-beta1 on the latest dependencies.

Steps to reproduce

$ composer outdated

Proposed resolution

$ composer update

Remaining tasks

Decide if we need to document the new dev-dependencies introduced by the update of open-telemetry/sdk, as discovered in the EDI-part of https://www.drupal.org/project/drupal/issues/3486545#comment-15851112, probably not

Confirmed by multiple core committers: No we don't.

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3486550

Command icon 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

spokje created an issue. See original summary.

spokje’s picture

spokje’s picture

$ composer-lock-diff --no-links
+----------------------+-------+-------+
| Production Changes   | From  | To    |
+----------------------+-------+-------+
| doctrine/annotations | 2.0.1 | 2.0.2 |
| guzzlehttp/promises  | 2.0.3 | 2.0.4 |
+----------------------+-------+-------+

+-----------------------------------+---------+---------+
| Dev Changes                       | From    | To      |
+-----------------------------------+---------+---------+
| composer/ca-bundle                | 1.5.2   | 1.5.3   |
| composer/composer                 | 2.8.1   | 2.8.2   |
| drupal/coder                      | 8.3.24  | 8.3.25  |
| lullabot/mink-selenium2-driver    | v1.7.3  | v1.7.4  |
| lullabot/php-webdriver            | v2.0.5  | v2.0.6  |
| mglaman/phpstan-drupal            | 1.2.12  | 1.3.1   |
| myclabs/deep-copy                 | 1.12.0  | 1.12.1  |
| nikic/php-parser                  | v5.1.0  | v5.3.1  |
| php-http/httplug                  | 2.4.0   | 2.4.1   |
| phpdocumentor/reflection-docblock | 5.4.1   | 5.5.1   |
| phpdocumentor/type-resolver       | 1.8.2   | 1.10.0  |
| phpstan/extension-installer       | 1.4.1   | 1.4.3   |
| phpstan/phpdoc-parser             | 1.29.1  | 1.33.0  |
| phpstan/phpstan                   | 1.12.4  | 1.12.10 |
| phpstan/phpstan-deprecation-rules | 1.2.0   | 1.2.1   |
| phpunit/phpunit                   | 10.5.35 | 10.5.38 |
| sebastian/comparator              | 5.0.2   | 5.0.3   |
| squizlabs/php_codesniffer         | 3.10.2  | 3.10.3  |
+-----------------------------------+---------+---------+
spokje’s picture

So

1) There are some new dev-dependencies, which is why 2 additions to the cspell dictionary are present.
2) One of these new dev-dependencies, tbachert/spi, needs permission to be in allow-plugins.

spokje’s picture

Besides tbachert/spi, I see four more new dev-dependencies:

1) brick/math:

$ composer why brick/math
ramsey/uuid 4.7.6 requires brick/math (^0.8.8 || ^0.9 || ^0.10 || ^0.11 || ^0.12)

2) nyholm/psr7-server:

$ composer why nyholm/psr7-server
open-telemetry/sdk 1.1.2 requires nyholm/psr7-server (^1.1)

3) ramsey/collection:

$ composer why ramsey/collection
ramsey/uuid 4.7.6 requires ramsey/collection (^1.2 || ^2.0)

4) ramsey/uuid

$ composer why ramsey/uuid
open-telemetry/sdk 1.1.2 requires ramsey/uuid (^3.0 || ^4.0)
ramsey/uuid        4.7.6 replaces rhumsaa/uuid (self.version)

So every one of the five new dev-dependencies come from open-telemetry/sdk.

Do we need to document this/all of the dependencies individually/ignore this completely?

EDIT: Hmmm, looking at https://www.drupal.org/about/core/policies/core-dependency-policies-and-... we:
a) are hopelessly behind on our current documentation.
b) trying to document all 5(?) current branches is going to be a slight nightmare.
c) also seem to have JS dependencies in that page (PostCSS)
d) seem to only document our direct dev-dependencies.

If d) is true, there won't be a need to document the new sub-dependencies IMHO.

spokje’s picture

Assigned: spokje » Unassigned
Status: Active » Needs review
spokje’s picture

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community

Don't see any issue, didn't seem to break anything.

longwave’s picture

Re #6 for dev dependencies at least I think documenting the direct ones only is fine. Given they only should be installed if you are running tests and they shouldn't have any effect on core itself then I don't think it's worth documenting implicit dependencies.

catch’s picture

#3478895: Document new Composer plugin tbachert/spi required by core-dev is open for the new composer plugin from tbachert/spi - tl;dr is it's not necessary to allow it but we might as well in core's composer.lock

#6 is pretty much the conclusion of #3084853: [policy] Document development dependencies - no need to document these.

spokje’s picture

spokje’s picture

Issue summary: View changes
spokje’s picture

Issue summary: View changes

  • catch committed f9d51f5c on 11.1.x
    Issue #3486550 by spokje: Update Composer dependencies for 11.1.0-beta1
    

  • catch committed 3d21bdfe on 11.x
    Issue #3486550 by spokje: Update Composer dependencies for 11.1.0-beta1
    

catch’s picture

Version: 11.x-dev » 11.1.x-dev
Status: Reviewed & tested by the community » Fixed

Committed/pushed to 11.x and cherry-picked to 11.1.x, thanks!

edit: crossposted, but this still applied cleanly even after the other issue landed.

  • catch committed 5ad48d86 on 11.1.x
    Revert "Issue #3486550 by spokje: Update Composer dependencies for 11.1....

  • catch committed fd5be152 on 11.x
    Revert "Issue #3486550 by spokje: Update Composer dependencies for 11.1....
spokje’s picture

edit: crossposted, but this still applied cleanly even after the other issue landed.

Rebased a while before I commented, in between that and your commit was first forgetting about and then frantically rerunning failed tests to get green again.
It all worked out just fine :)

catch’s picture

Status: Fixed » Needs work

Sorry immediately after committing this I saw #3484463: Upgrade open-telemetry packages for PHP 8.4 which is adding some vendor hardening for the new spi dependency, so I reverted here and committed that issue to get that change in.

I'm not sure how much is left here but it'll need another rebase..

spokje changed the visibility of the branch 3486550-update-composer-dependencies to active.

spokje’s picture

Status: Needs work » Reviewed & tested by the community

Rebased and updated #4.

  • longwave committed 2573842c on 11.1.x
    Issue #3486550 by spokje, catch: Update Composer dependencies for 11.1.0...

  • longwave committed 21e720a9 on 11.x
    Issue #3486550 by spokje, catch: Update Composer dependencies for 11.1.0...
longwave’s picture

Status: Reviewed & tested by the community » Fixed

beta1 is due this week - we have skipped the alpha due to time constraints - so this is probably the last round until rc1 or maybe even just the final release.

Committed 21e720a and pushed to 11.x. Thanks!

Committed 2573842 and pushed to 11.1.x. Thanks!

Status: Fixed » Closed (fixed)

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