[PH-39] Use new component version in PrimeHub install script #741
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
huaichehuang
force-pushed
the
bug-PH-39-update-primehub-install-script
branch
from
af24097
to
6c8edb5
Compare
Signed-off-by: Dennis Huang <[email protected]>
Signed-off-by: Dennis Huang <[email protected]>
huaichehuang
force-pushed
the
bug-PH-39-update-primehub-install-script
branch
from
6c8edb5
to
6e16339
Compare
Signed-off-by: Dennis Huang <[email protected]>
Signed-off-by: Dennis Huang <[email protected]>
Signed-off-by: Dennis Huang <[email protected]>
Signed-off-by: Dennis Huang <[email protected]>
Signed-off-by: Dennis Huang <[email protected]>
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.
** PR checklist **
What type of PR is this?
Bug
What this PR does / why we need it:
To meet the current support version of each component used by PrimeHub
Which issue(s) this PR fixes:
Typo and outdated component versions
Does this PR introduce a user-facing change?:
NONE
Assignees
@huaichehuang