Skip to content

[Bug] Stabilize class mapping checksum across array key order#419

Draft
mcop1 wants to merge 2 commits into
2.5from
order_fields_on_hash_compute
Draft

[Bug] Stabilize class mapping checksum across array key order#419
mcop1 wants to merge 2 commits into
2.5from
order_fields_on_hash_compute

Conversation

@mcop1

@mcop1 mcop1 commented Apr 27, 2026

Copy link
Copy Markdown
Contributor

Recursively sort associative array keys before hashing the class mapping so that PHP insertion order changes do not produce a different checksum, which would otherwise trigger spurious reindex runs for unchanged class definitions.

Recursively sort associative array keys before hashing the class
mapping so that PHP insertion order changes do not produce a different
checksum, which would otherwise trigger spurious reindex runs for
unchanged class definitions.
@mcop1 mcop1 self-assigned this Apr 27, 2026
@mcop1 mcop1 added the Bug label Apr 27, 2026
@mcop1 mcop1 changed the base branch from 2026.x to 2.5 April 27, 2026 08:10
The setup-matrix job was using the default checkout (merge commit), which
reads composer.json from the base branch. The reusable codeception workflow
checks out the PR head ref instead. When the base branch allows a newer PHP
version (e.g. 8.5) that the PR branch does not support, the matrix includes
PHP versions incompatible with the PR's composer.json, causing composer to
fail.

Pin the setup-matrix checkout to the PR head sha so both jobs use the same
composer.json and the generated matrix matches the code being tested.
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants