It produced tons of tags "v0.0.1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-fix-apicalls2-0-0-0-0-0-0-0-0-0-0-0.0"

Nobody has claimed this yet.

Github Action:

I put the example from the README in a workflow and the result was tons of tags, one longer than the previous one, concatenating all these tag-names all together with every iteration:

```
name: Bump version
on: [push]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Bump version and push tag
id: tag_version
uses: mathieudutour/github-tag-action@v6.2
with:
github_token: ${{ secrets.TOKEN }}
- name: Create a GitHub release
uses: ncipollo/release-action@v1
with:
tag: ${{ steps.tag_version.outputs.new_tag }}
name: Release ${{ steps.tag_version.outputs.new_tag }}
body: ${{ steps.tag_version.outputs.changelog }}

```

Start by reproducing the README workflow from the issue, including the checkout, github-tag-action step, and release step, then inspect how the action derives its new_tag from existing tags. Done means repeated workflow runs produce one correctly formatted, non-recursive version tag rather than concatenating prior tag names.

Written by the indexing model from the issue text.