UPSTREAM FIX

magento2-40880: Di.xml array items being replaced when a later module uses the item name 0

Community fix magento2-40880 merged into magento/magento2 on 2026-08-14, not in a release yet; applies cleanly to 34 releases from 2.4.6 to 2.4.9.

Fixes di.xml array items being replaced when a later module uses the item name 0 edited

Pull request title: di.xml array item gets replaced if later config used numeric key
Pull request: magento/magento2#40880
Issues: #36861 human
Author: @aasim110
Merged: 2026-08-14
Fixed in: no release yet
Reported on: —
Categories: —
Components: magento/framework

Labels

Area: Framework
Component: —
Priority: P2
Severity: —
Reported on (labels): 2.4.x

Issue

Title and steps come from the upstream issue and pull request.

Description

DI contains only values from second module

array (
    '_v_' =>
        array (
            0 => 'some_val_2',
            'some_other_key' => 'some_val_3',
        ),
)

Steps to reproduce

1. Create moduł A with DI.xml

    <type name="Some\Class">
        <arguments>
            <argument name="someArgumentName" xsi:type="array">
                <item name="some_key_1" xsi:type="const">some_val_1</item>
            </argument>
        </arguments>
    </type>

2. Create module B with DI.xml

    <type name="Some\Class">
        <arguments>
            <argument name="someArgumentName" xsi:type="array">
                <item name="0" xsi:type="const">some_val_2</item>
                <item name="some_other_key" xsi:type="const">some_val_3</item>
            </argument>
        </arguments>
    </type>

3. Compile di with setup:di:compile
4. Check generated metadata cat generated/metadata/graphql.php | grep "someArgumentName" -A 10

Expected result

Generated DI must look contain all values. Smth like this

array (
    '_v_' =>
        array (
            'some_key_1' => 'some_val_1',
            0 => 'some_val_2',
            'some_other_key' => 'some_val_3',
        ),
)

Actual result

DI contains only values from second module

array (
    '_v_' =>
        array (
            0 => 'some_val_2',
            'some_other_key' => 'some_val_3',
        ),
)

Taken from the upstream issue.

Code match per tag

Each tag was checked with git apply --check against that tag's files. A clean match means the change applies; it is not a test result. Tags that already contain the fix are marked.

Line	Code match per tag	Tests
2.4.6	2.4.6 clean 2.4.6-p1 clean 2.4.6-p2 clean 2.4.6-p3 clean 2.4.6-p4 clean 2.4.6-p5 clean 2.4.6-p6 clean 2.4.6-p7 clean 2.4.6-p8 clean 2.4.6-p9 clean 2.4.6-p10 clean 2.4.6-p11 clean 2.4.6-p12 clean 2.4.6-p13 clean 2.4.6-p14 clean 2.4.6-p15 clean	2.4.6: no test data 2.4.6-p1: no test data 2.4.6-p2: no test data 2.4.6-p3: no test data 2.4.6-p4: no test data 2.4.6-p5: no test data 2.4.6-p6: no test data 2.4.6-p7: no test data 2.4.6-p8: no test data 2.4.6-p9: no test data 2.4.6-p10: no test data 2.4.6-p11: no test data 2.4.6-p12: no test data 2.4.6-p13: no test data 2.4.6-p14: no test data 2.4.6-p15: no test data
2.4.7	2.4.7 clean 2.4.7-p1 clean 2.4.7-p2 clean 2.4.7-p3 clean 2.4.7-p4 clean 2.4.7-p5 clean 2.4.7-p6 clean 2.4.7-p7 clean 2.4.7-p8 clean 2.4.7-p9 clean 2.4.7-p10 clean	2.4.7: no test data 2.4.7-p1: no test data 2.4.7-p2: no test data 2.4.7-p3: no test data 2.4.7-p4: no test data 2.4.7-p5: no test data 2.4.7-p6: no test data 2.4.7-p7: no test data 2.4.7-p8: no test data 2.4.7-p9: no test data 2.4.7-p10: fails before, passes afterunit: fails before, passes after
2.4.8	2.4.8 clean 2.4.8-p1 clean 2.4.8-p2 clean 2.4.8-p3 clean 2.4.8-p4 clean 2.4.8-p5 clean	2.4.8: no test data 2.4.8-p1: no test data 2.4.8-p2: no test data 2.4.8-p3: no test data 2.4.8-p4: no test data 2.4.8-p5: fails before, passes afterunit: fails before, passes after
2.4.9	2.4.9 clean	2.4.9: fails before, passes afterunit: fails before, passes after

Triage

Model @cf/cloudflare/clef. Probability this is a bug fix: 98.0%. Probability it is security relevant: 0.6%.

Show the model's answers and probabilities

Question	Answer	Probabilities	Confidence
Change kind	bugfix	bugfix 96.3%, refactor 1.1%, tests_only 1.0%, feature 0.7%, dependency 0.5%, docs_only 0.4%	91.4%
Area	framework	framework 97.3%, graphql_api 0.7%, admin 0.7%	93.8%
Reported version	unspecified	unspecified 51.8%, 2.4.6 1.5%, 2.4.6-p1 1.1%	26.3%
Scope	1.15 of 2	1 41.0%, 2 36.8%, 0 22.1%	3.0%
Risk	0.59 of 2	0 50.3%, 1 40.8%, 2 8.9%	14.1%
Worth backporting	1.54 of 2	2 63.7%, 1 26.1%, 0 10.1%	22.7%

Download

For cweagans/composer-patches, choose a version below and download the bundle. Copy its magento2-40880/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Test files are always removed; paths are relative to each package root, using the default -p1 level.

Bundle README (what the ZIP ships)

# magento2-40880

Community fix merged upstream into magento/magento2, adapted by magento.watch.
This is not a patch published by Adobe.

Pull request: https://github.com/magento/magento2/pull/40880
Issue: https://github.com/magento/magento2/issues/36861
Author: @aasim110
Source commit: 7ef87fb813c21e066a696c63d24f4a6bcd01bbe6
Modifications: test files and documentation removed, paths rewritten relative to each Composer package.
Licence: OSL-3.0 / AFL-3.0, as the original Magento Open Source code.
Maintainer: Łukasz Bajsarowicz (@lbajsarowicz)

Licence: Magento Open Source code under OSL-3.0 and AFL-3.0. The bundle carries the original author, source commit and the list of modifications.