feat: add GitHub release badge and trigger 0.1.60 release#16
Merged
Conversation
sai-kumar-peddireddy
added
the
enhancement
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
1 participant
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.
This PR adds a GitHub release badge to the README and triggers the 0.1.60 release.
What this does
Why version 0.1.60?
The previous release (0.1.2.74) was not indexed by Jenkins Update Center because 0.1.2 < 0.1.59 in semantic versioning. Version 0.1.60 is higher than 0.1.59, ensuring proper Update Center indexing.
This PR has the enhancement label to ensure the CD workflow recognizes it as an interesting change and creates the release.