Question about latest version retrieval using github actions (no npm) and git-tags

I [tried to setup `auto`](https://github.com/physiopy/phys2bids/pull/313) in a [python repository](https://github.com/physiopy/phys2bids), without using npm - downloading the latest release from github - with [this Github action](https://github.com/physiopy/phys2bids/blob/master/.github/workflows/auto-release.yml).
From the last [log of the action](https://github.com/physiopy/phys2bids/runs/1255256249?check_suite_focus=true#step:4:512), the [one before](https://github.com/physiopy/phys2bids/runs/1254712841?check_suite_focus=true#step:4:503), and the [first one after merging `auto`](https://github.com/physiopy/phys2bids/runs/1254668371?check_suite_focus=true) , it seems like auto retrieves the latest release correctly, but then:
- it seems like the labels are not set in the repository, when they are (I ran `auto create-labels` a couple of times to be sure)
- it seems like it uses the version before the last one to compute the new version
- it fails because the version it computed already exists.

Am I missing something in the configuration files?

Start with the linked .github/workflows/auto-release.yml and the three referenced GitHub Actions logs. Compare the repository's configured labels, latest release, and git tags with the version that auto calculates; done means identifying whether the failure is configuration-related or a reproducible auto defect.

Written by the indexing model from the issue text.