[stable19] Use composer v1 on CI#531
Merged
ChristophWurst merged 1 commit intostable19from Nov 23, 2020
Merged
Conversation
ChristophWurst
changed the title
ChristophWurst
force-pushed
the
fix/stable19-ci-composer-v1
branch
from
11fb00f to
aea4cef
Compare
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
ChristophWurst
force-pushed
the
fix/stable19-ci-composer-v1
branch
from
aea4cef to
149ada8
Compare
skjnldsv
approved these changes
Nov 23, 2020
Member
Author
|
/backport to stable20 |
Member
Author
|
/backport to stable18 |
|
The backport to stable18 failed. Please do this backport manually. |
This was referenced Dec 1, 2020
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
#530 fails with weird composer diffs. Maybe we should use v1 for the old branches.