Remove deprecated BUILT_BRANCH_SUFFIX input
#147
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
shvlv
reviewed
Aug 8, 2024
Co-authored-by: Volodymyr Shelmuk <[email protected]> Signed-off-by: Philipp Bammes <[email protected]>
shvlv
approved these changes
Aug 8, 2024
luislard
reviewed
Aug 12, 2024
Chrico
approved these changes
Aug 22, 2024
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature
Closes #146
What is the current behavior? (You can also link to an open issue here)
The deprecated
BUILT_BRANCH_SUFFIXinput is present. All calling workflows have been updated to use the newerBUILT_BRANCH_NAME.What is the new behavior (if this is a feature change)?
The
BUILT_BRANCH_SUFFIXinput is removed.Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Yes, but no package uses the deprecated input anymore.
Other information:
I haven't tested this, so I'd appreciate it if one of you could give this a spin. Thanks!