Added TAG_PREFIX so more descriptive tags can be used

[timothyclarke]

Summary of changes

Added TAG_PREFIX to replace WITH_V. WITH_V is still in place for backwards comparability, but the idea is it would be removed in a few versions (gives people a chance to change their code, doesn't force a major etc)

This should fix #320. I have a similar use case where a monorepo has a bunch of folders which maintain independent versions

This is best used along side changed-files and a matrix

Breaking Changes

Do any of the included changes break current behaviour or configuration?

NO : The changes are backwards compatible to allow a smoother transition

How changes have been tested

Backwards compatibility
tagging WITH_V false
tagging WITH_V true

New Feature (all in matrix jobs as that's my usecase)
Bump multiple tags
Bump one tag add one tag

List any unknowns

[timothyclarke]

@anothrNick When you get a chance can you take a look at this one please

[yannickpoggel]

Hi @anothrNick , this feature would be great for working with monorepos.

[robw-raviga]

Suggested change

	- **WITH_V** _(optional, depricated)_ - Tag version with `v` character. Replaced by TAG_PREFIX
	- **WITH_V** _(optional, deprecated)_ - Tag version with `v` character. Replaced by TAG_PREFIX

[TimothyClarkeTide]

@robw-raviga Thanks. Fixed in ed6507f

[dethell]

Any chance this can get merged? It's the only thing holding our team up from using this in our monorepo.

[anothrNick]

@timothyclarke @yannickpoggel @dethell Approved. I will merge and deploy.

[anothrNick]

Should be available in 1.72.0

[rorybartie]

@anothrNick and @timothyclarke It seems like this PR is causing 2 v's to be prefixed to the tag if you are still using the WITH_V: true tag in your workflows. The tag ends up looking something like this vv0.2.0-dev.0. This in turn then causes the next run of the action to fail because it tries to create the same tag again.
Here is an example output from the failing action:

Setting dev pre-tag v2.19.1-dev.0 - With pre-tag vv2.20.0-dev.0
EVENT: creating local tag vv2.20.0-dev.0
Updated tag 'vv2.20.0-dev.0' (was 98cfac70)
EVENT: pushing tag vv2.20.0-dev.0 to origin
2025-05-09T09:04:15Z: **pushing tag vv2.20.0-dev.0 to repo repo_name
  "message": "Reference already exists",
  "documentation_url": "https://docs.github.com/rest/git/refs#create-a-reference",
  "status": "422"
}

In this case the tag vv2.20.0-dev.0 was already created in a previous run.

[rorybartie]

This is where the bug comes in. ${new} already has the tag prefix.