Gitea Actions: Trigger workflow not started

I create next workflow
https://try.gitea.io/dimon_ukr/test/src/branch/main/.gitea/workflows/on_tag.yaml

name: Pipeline Name Here
run-name: ${{ gitea.actor }} is testing out Gitea Actions πŸš€
on:
  push:
    tags:
      - 'v*'

jobs:
  RunTests:
    name: Run Tests
    runs-on: ubuntu-latest
    steps:
      - run: |
          echo 'Hello Release'
          env | sort          

and yet workflow
https://try.gitea.io/dimon_ukr/test/src/branch/main/.gitea/workflows/set_tag.yaml

name: Pipeline Name Here
run-name: ${{ gitea.actor }} is testing out Gitea Actions πŸš€
on:
  push:

jobs:
  Test:
    name: Test
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Push tag v1
        run: |
          git config user.email "${{ github.event.head_commit.author.email }}"
          git config user.name "${{ github.event.head_commit.author.name }}"

          git tag v1 -a -m "MESSAGE"
          git push origin v1          

      - name: Set Tag v2
        run: |
          TAG="${INPUT_TAG}"
          OWNER="${INPUT_OWNER:-$GITHUB_REPOSITORY_OWNER}"
          TOKEN="${INPUT_TOKEN:-$GITHUB_TOKEN}"
          TARGET="${INPUT_SHA:-$GITHUB_SHA}"
          MESSAGE="${INPUT_MESSAGE:-"Release $INPUT_TAG"}"
          CODE=$(curl --write-out '%{http_code}' --output /dev/null --silent --user ${OWNER}:${TOKEN} -X POST -H "accept: application/json" -H "Content-Type: application/json" ${GITHUB_SERVER_URL}/api/v1/repos/${GITHUB_REPOSITORY}/tags -d "{\"message\": \"${MESSAGE}\", \"tag_name\": \"$TAG\", \"target\": \"$TARGET\"}")
          echo $CODE
          if [ '201' -ne $CODE ]; then
            exit 1
          fi          
        with:
          tag: v2

if i create tag from ui then workflow started but if tag set by another workflow by push tag or call API then workflow NOT STARTED.

What can i do to fix this issue?

Looks like you have fixed your problem dimon_ukr/test - test - Gitea: Git with a cup of tea ?

May be.
I found on stackoverflow hack for this situation.

Need use PAT token for step checkout with permission for read and write repo.

But which method is TRUE for solve this problem? With create release same situation - workflow not started :frowning: …