Fix #24019

[korostii]

Description (*)

Update $this->patchesRegistry in real-time in order to prevent patches from being applied multiple times.
Consecutively, \Magento\Framework\Setup\Patch\PatchRegistry::registerPatch() will recognize that these patches were previously applied through a $this->patchHistory->isApplied($patchName) call.

Fixed Issues (if relevant)

1. Declarative schema: Patch dependencies can cause a patch to apply twice #24019: Declarative schema: Patch dependencies can cause a patch to apply twice

Manual testing scenarios (*)

Please see #24019 for detailed steps.

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @korostii. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Guide documentation.

[VladimirZaets]

Hi @korostii. Thanks for collaboration. Due to Magento Definition of Done all code must be covered by tests. Please cover your fix by automated tests.

[magento-engcom-team]

Hi @VladimirZaets, thank you for the review.
ENGCOM-6198 has been created to process this Pull Request

[engcom-Alfa]

✔️ QA Passed

Before:

After:

[m2-assistant]

Hi @korostii, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.