fix(release): stop tagging bot-api version

Debug log from run 25609309601 confirmed semver-generator picks the chronologically most-recent tag as the version base. Whenever the bot-api-vX.Y tag was created after the library tag (or recreated during a partially-failing release), semver-generator picked bot-api-v10.0 as the base, couldn't parse 'v10.0' as full SemVer (no patch number), and restarted numbering from v0.0.x. Per direct user instruction: drop the bot-api tag entirely. The Bot API version still appears in the library tag message and release notes. Also delete the existing bot-api-v10.0 tag from local + remote so the next release sees only v* tags.
chore(release): add tag-fetch step + debugmode to diagnose semver
2026-06-06 22:49:32 +00:00 · 2026-05-09 20:06:02 +01:00 · 2026-05-09 20:02:10 +01:00 · 2026-05-09 19:58:14 +01:00 · 2026-05-09 19:51:34 +01:00
1 changed files with 7 additions and 13 deletions
@@ -245,23 +245,17 @@ jobs:
          API_TAG: ${{ steps.api_version.outputs.tag }}
          API_VER: ${{ steps.api_version.outputs.version }}
        run: |
+          # Bot API version (currently $API_VER) is intentionally NOT
+          # tagged separately. semver-generator picks the most recent
+          # tag as the version base; a non-SemVer marker like
+          # bot-api-vX.Y poisons that and restarts numbering from
+          # v0.0.x. Bot API version stays as a comment in the lib tag
+          # message and in the release notes.
          git config user.name  "github-actions[bot]"
          git config user.email "github-actions[bot]@users.noreply.github.com"
-          git tag -a "$LIB_TAG" -m "Release $LIB_TAG"
+          git tag -a "$LIB_TAG" -m "Release $LIB_TAG (Bot API $API_VER)"
          git push origin "$LIB_TAG"

-          if [ -n "$API_TAG" ]; then
-            # Force-update the bot-api tag so it always points at the latest
-            # release that supports that API version.
-            if git rev-parse "$API_TAG" >/dev/null 2>&1; then
-              git tag -f -a "$API_TAG" -m "go-telegram release $LIB_TAG (Bot API $API_VER)"
-              git push -f origin "$API_TAG"
-            else
-              git tag -a "$API_TAG" -m "go-telegram release $LIB_TAG (Bot API $API_VER)"
-              git push origin "$API_TAG"
-            fi
-          fi
-
      - name: Run GoReleaser
        if: github.event_name != 'workflow_dispatch' || inputs.dry-run-release == false
        uses: goreleaser/goreleaser-action@v6
Author	SHA1	Message	Date
lukaszraczylo	6f9b29ea0c	fix(release): stop tagging bot-api version Debug log from run 25609309601 confirmed semver-generator picks the chronologically most-recent tag as the version base. Whenever the bot-api-vX.Y tag was created after the library tag (or recreated during a partially-failing release), semver-generator picked bot-api-v10.0 as the base, couldn't parse 'v10.0' as full SemVer (no patch number), and restarted numbering from v0.0.x. Per direct user instruction: drop the bot-api tag entirely. The Bot API version still appears in the library tag message and release notes. Also delete the existing bot-api-v10.0 tag from local + remote so the next release sees only v* tags.	2026-05-09 20:06:02 +01:00
lukaszraczylo	bd80af240d	chore(release): add tag-fetch step + debugmode to diagnose semver Add an explicit git fetch --tags --force origin before semver-generator runs, plus log visible tags. Enable semver-generator's debugmode so the failure mode is visible. Diagnostic only — once we understand why semver-generator computes v0.0.2 despite v0.1.2 being the latest tag, the debug step can be removed.	2026-05-09 20:02:10 +01:00
lukaszraczylo	af180b75c5	fix(release): tag bot-api marker before library version semver-generator picks the chronologically most-recent tag as the version base. The previous order tagged the lib version first, then bot-api-vX.Y, leaving the bot-api tag as the most recent. semver- generator then treated 'vX.Y' as the base, couldn't parse it as full SemVer (no patch number), and silently restarted numbering from v0.0.x — causing surprise version downgrades like v1.1.1 -> v0.0.4 and v0.1.1 -> v0.0.2. Tagging bot-api-vX.Y first and the library version last keeps the library tag as the chronologically last one, so subsequent runs see it as the version base and bump correctly.	2026-05-09 19:58:14 +01:00
lukaszraczylo	29bf575cfd	chore(release): bump to v0.1.2 Empty commit to advance the auto-release pipeline. Latest tag was v0.1.1; semver-generator with the patch-prefix in the subject computes the next version as v0.1.2.	2026-05-09 19:51:34 +01:00