GH-26: Fixed ignored release_name
option.
#27
Merged
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.
name
should be used when creating a new release.Signed-off-by: Akos Kitta [email protected]
What it does:
repo_name
property when creating a new GH release:repo_name
was incorrectly used instead ofname
. [Closes release_name does not seem to apply #26]package-lock.json
file with the desired2.1.0
version.PoC:
@svenstaro can you please review the changes? Thank you!