Adapted ezbehat runner to Composer 2.2 #247
Merged
Conversation
This file contains 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
mnocon
force-pushed
the
adapt-to-composer-2.2
branch
from
18c55f3
to
dc61641
Compare
mnocon
requested review from
bogusez,
kacper-wieczorek-ibexa,
katarzynazawada,
micszo,
piotrbisaga and
tomaszszopinski
tomaszszopinski
approved these changes
Jan 5, 2022
micszo
approved these changes
Jan 5, 2022
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.
Composer 2.2.2 changes the working directory when binaries are executed:
composer/composer#10389
composer/composer#10402
It's also mentioned in the release notes for Composer 2.2.2:
https://github.com/composer/composer/releases/tag/2.2.2
This PR updates our ezbehat runner so that it relies on
COMPOSER_BIN_DIR, notBASH_SOURCESenv variable.