Merge 2.4.4 master into develop #422
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MFTF 2.4.1 - Merge develop to master
added file name suffix principle for data
MFTF 2.4.2 - Merge develop to master
SMALL_CHANGE: Minor change suggested
MFTF 2.4.3 - Merge to Master
Adding topic for Action Group reference.
Temp removal of files to fix build.
Removes a duplicated ID from header
MQE-1691: CREDS resolution does not occur from Suite <before>
- Version bump and changelog addition.
MQE-1699: CHANGELOG.MD and Composer version bump
MFTF 2.4.4 - Merge to Master
KevinBKozan
approved these changes
Aug 15, 2019
magento-devops-reposync-svc
pushed a commit
that referenced
this pull request
Dec 13, 2024
PHP 8.4: deprecation fixes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR we merge master into develop so that our 2.4.4 release changes are in develop too.
There was a conflict in composer.lock which I resolved manually by generating a new
content-hash