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
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:
- 3486550-update-composer-dependencies
changes, plain diff MR !10122
Comments
Comment #2
spokjeComment #4
spokjeComment #5
spokjeSo
1) There are some new dev-dependencies, which is why 2 additions to the
cspelldictionary are present.2) One of these new dev-dependencies,
tbachert/spi, needs permission to be inallow-plugins.Comment #6
spokjeBesides
tbachert/spi, I see four more new dev-dependencies:1)
brick/math:2)
nyholm/psr7-server:3)
ramsey/collection:4)
ramsey/uuidSo 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.
Comment #7
spokjeComment #8
spokjeComment #9
smustgrave commentedDon't see any issue, didn't seem to break anything.
Comment #10
longwaveRe #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.
Comment #11
catch#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.
Comment #12
spokjeRebased after #3486184: Update to Symfony 7.2.0-BETA2 landed.
Comment #13
spokjeComment #14
spokjeComment #18
catchCommitted/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.
Comment #21
spokjeRebased 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 :)
Comment #22
catchSorry 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..
Comment #25
spokjeRebased and updated #4.
Comment #28
longwavebeta1 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!