ci: Extra Git Tags Created for Releases Causing Incorrect Semantic Versions in Binaries

[walldiss]

Implementation ideas

Issue Summary:
Starting from version v0.18.3-mocha, additional unintended tags are being created for the same pull request (PR). These extra tags are misleading and are being used as semantic versions in the binaries instead of the intended proper version tags.

Affected Releases:

• v0.18.3-mocha:

  • v0.18.0-refs-tags-v0-18-3-mocha.0
  • v0.18.3-mocha

• v0.19.0-arabica:

  • v0.18.0-refs-tags-v0-19-0-arabica.0
  • v0.19.0-arabica

Root Cause:
The issue appears to have started due to the Release CI action running the bump version action on pre-releases.
[Commit 395ba5f](#3855)

Impact:

• Misleading Tags: Extra tags like v0.18.0-refs-tags-v0-18-3-mocha.0 are being treated as semantic versions.
• Incorrect Binaries: These misleading tags are injected into the binaries, causing confusion and potential issues in version tracking and dependency management.

Expected Behavior:
Each release should have a single, clear semantic version tag (e.g., v0.18.3-mocha or v0.19.0-arabica) without additional prefixed or suffixed tags.