Why pushing branch when it's only a new tag and no commits?

[aparij]

I'm specifying those options with semver v3.0

push: true
skipProjectChangelog: true
skipRootChangelog: true
skipCommit: true

Basically I just want to push a tag with no changelog or any other commits.

[ts-example] 🆕 Calculated new version "0.1.249".
[ts-example] 🔖 Tagged "ts-example-0.1.249".
[ts-example] 🟠 Git push --atomic failed, attempting non-atomic push.
[ts-example] ❌ Error: Locking support detected on remote "origin". Consider enabling it with:
$ git config lfs.https://git.XXXXX/lfs.locksverify true
To git.XXXX.git

• [new tag] ts-example-0.1.249 -> ts-example-0.1.249
  ! [rejected] ticket/fix_versioning -> ticket/fix_versioning (non-fast-forward)
  error: failed to push some refs to 'git.XXXXX.git'

It manages to create and push the new tag * [new tag] ts-example-0.1.249->ts-example-0.1.249
but fails to push to origin, it is rejected because there are some other new commits on the branch, it failed for a good reason.

In another case when it can push (no new commits on the branch) it is successful:
[ts-example] 🚀 Pushed to "origin" "ticket/fix_versioning".

But nothing really get pushed to the branch.

The question is why it tries to push the branch itself, pushing the tag only is enough since skipCommit:true
Is it because it just does git push or something and not specifying just the tag to push?
Is it because it tries to prevent orphan tags and needs to push the branch because the commit needs to be pushed as well since the tag is on the commit?

Do I need some other configuration to prevent it from pushing branch (I still need to have push:true because it pushes the tag)?
In general I can handle the failed command because it still pushes the new tag ( and commit is already on the remote branch), but I prefer not to write code to handle failures that should work.