Closed
Conversation
During 4.20 release cycle, 4.18.34 was made default in RP Config. This change sets 4.18.34 as the default for local rp development and e2e pipelines. Closes: ARO-25103
yadneshk
requested review from
alcasim,
bennerv,
cadenmarchese,
hawkowl,
hlipsig,
jharrington22,
kimorris27,
mociarain,
mrWinston,
rogbas,
sankur-codes,
tiguelu,
tsatam,
tuxerrante,
ventifus,
wanghaoran1988 and
yjst2012
as code owners
Collaborator
Collaborator
Author
|
Closing this in favour of #4655 |
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
2 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.
During 4.20 release cycle, 4.18.34 was made default in RP Config. This change sets 4.18.34 as the default for local rp development and e2e pipelines.
Which issue this PR addresses:
Fixes ARO-25103
What this PR does / why we need it:
Since 4.17 reaches EOL (Stable Channel) on April 1, it becomes mandatory to make 4.18.34 as the default version during this release cycle
Test plan for issue:
Test these changes in canary.
Is there any documentation that needs to be updated for this PR?
No.
How do you know this will function as expected in production?
After verifying in canary.