Needs work
Project:
Drupal core
Version:
main
Component:
base system
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Oct 2026 at 19:26 UTC
Updated:
17 Oct 2026 at 00:43 UTC
Jump to comment: Most recent
Problem/Motivation
#3566600: Deprecate drupal/core-dev-pinned metapackage and #3575461: Cleanup any remaining deprecations removed updates of the PinnedDevDependencies metapackage, but left the stale composer.json in as well as did not adjust EnsurePHPStanVersionsMatchTest.
This is causing packaging issues and test failures of the PHPStan rules.
Steps to reproduce
Composer update phpstan and see failures in PHPStan rule tests.
Proposed resolution
Remove the stale composer.json and adjust the test.
Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
Issue fork drupal-3631365
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:
changes
Comments
Comment #3
mondrakeComment #4
mondrakeComment #5
godotislateThis looks right, but I'm not sure how this affects the subtree pushes. Presumably it should be correct to stop pushing them for 12.x? Somehow the https://github.com/drupal/core-dev-pinned repo has a 12.0.0-beta2 from three weeks ago, https://github.com/drupal/core-dev-pinned/releases/tag/12.0.0-beta2, even though the core release was yesterday.
Comment #6
mondrakeMore cleanup.
Comment #7
longwaveThe subtree splitter runs during the packaging process and as I understand it should just ignore this package as soon as we remove it from core. Only the DA have access to packaging logs so the only real way to find out is commit and see what happens.
One question on the MR.
Comment #8
xjm@drumm located the code that would need to be cbanged in packaging:
https://gitlab.com/drupal-infrastructure/subtree-splitter/-/blob/e0d13fe...