Release draft uses wrong tag

[sholladay]

Description

The tag that np uses in the release draft template is based on the raw input of the user on the command line, rather than the actual tag being used during the release. This causes the release draft to be broken for users who increment the package version by semver type instead of providing a predetermined version number. For example, running np major instead of np 1.0.0.

Steps to reproduce

1. Run np major (or any other increment type, such as patch)
2. See the release draft refers to a vmajor tag, which does not exist

Expected behavior

The release draft must use the resolved tag/version number, as determined by npm, not merely the raw user input.

Environment

np - 5.0.3
Node.js - 12.4.0
npm - 6.9.0
Git - 2.22.0
OS - macOS 10.13.6

[sindresorhus]

// @yaodingyd

[yaodingyd]

Confirmed. Working on a fix.