iTwin
Add previous-minor Release Tag
Currently when patching a previous minor branch (for example, release/5.2.x when the latest is release/5.3.x), no release tag is added when publishing packages to npm. This then means that npm automatically adds the "latest" tag to the package even though it is not actually the latest version. To fix this, the "previous-minor" tag was created for patching previous minors. Open to discussion on other names for this tag, however "previous" is already applied to previous major versions so that can't be used. "lts" (long term support) is used often and could be applied to either the previous minor or previous major if desired.
logic looks good. Is the tag shown the one that will be on npm? Also I assume we don't need to change any other pipelines to respond to this new tag? This tag is passed all the way down to publish step?
logic looks good. Is the tag shown the one that will be on npm? Also I assume we don't need to change any other pipelines to respond to this new tag? This tag is passed all the way down to publish step?
Right, this tag is the one that will be shown on npm, and it should be passed down automatically to the publish step.
Any objections to "previous-minor" as the name of the tag?
Seems good to me since we already use "previous"
Any objections to "previous-minor" as the name of the tag?
Seems good to me since we already use "previous"
Should we just use "previous" tag instead of "previous-minor" ? I don't think, "previous" tag serves any real purpose now.
My problem with "previous-minor" is more of a nitpick, but what if we don't need to backport anything to previous minor for a few minor versions ? "previous-minor" would be stuck on something like 5.5.x while 5.8.x is out, which means actual previous minor would be 5.7.x. Again, tags are close to meaningless in my opinion (with exception of "latest"), so this may not matter.
