yum: fix target artifact name #896
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
Contributor
Author
|
TODO: need to tweak |
It should be without -lts- for fluent-release package Signed-off-by: Kentaro Hayashi <[email protected]>
Contributor
Author
|
It might be better to use unique artifact name between master (v6) and v5. |
daipom
approved these changes
Aug 27, 2025
Contributor
daipom
left a comment
daipom
left a comment
There was a problem hiding this comment.
Thanks!
Note: We will manage fluent-release for v5 normal channel on this branch exceptionally (although it is not related to v5 LTS)
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.
It should be without -lts- for fluent-release package