Publish Workflow creates duplicate tags

[mwbrooks]

Description

The publish workflow is created duplicate tags. The manual release steps creates a semver tag (e.g. v1.20.0) while the JasonEtco/build-and-tag-action action creates a second tag that's missing the patch (e.g. v1.20).

We may be able to fix this by specifying the tag name in the JasonEtco/build-and-tag-action action.

What type of issue is this? (place an x in one of the [ ])

• [x] bug
• [ ] enhancement (feature request)
• [ ] question
• [ ] documentation related
• [ ] example code related
• [ ] testing related
• [ ] discussion

Requirements (place an x in each of the [ ])

• [x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
• [x] I've read and agree to the Code of Conduct.
• [x] I've searched for any related issues and avoided creating a duplicate issue.

[filmaj]

Even with using the with: tag_name: tagname specifier for this action, it still seems like it is an issue (still happened for the v1.22.0 release).

[filmaj]

I filed https://github.com/JasonEtco/build-and-tag-action/issues/42 for this.

[zimeg]

:thinking: Could this be expected behavior to allow folks to pin a specific patch version or just use the latest patch of a minor version?

[filmaj]

Yeah I think so