Fix: skip v1.3.1 following mismatch between manifest and tags in github dating back from may #157
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
Collaborator
Author
|
@eleniv3d FYI I had this problem when making the new release ;) When creating a tag in GitHub, it should be the same as in the manifest.yml :) |
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.
a 1.3.1 tag from 28th of may did not include an update of the version to the manifest.yml: https://github.com/diffCheckOrg/diffCheck/releases/tag/v1.3.1, leading to issues when creating new release because the manifest does not contain the new version number and the versionize invoke fails due to no difference in previous and new version number.