fix: select the release tag by version instead of by tagged commit

[yeelali14]

Problem

The release job on develop failed after #566 merged (run):

HTTP 422: Validation Failed
Release.tag_name already exists
tag_name was used by an immutable release      NEW_TAG: 2.0.257

2.0.257 was already released on 08-06. tag-version.sh recomputed it because three tags point at the same commit f6ecd22:

2.0.256 → f6ecd22
2.0.257 → f6ecd22
v2      → f6ecd22

It read the latest version with git describe --tags $(git rev-list --tags --max-count=1) — whichever tag git happens to name on the newest tagged commit. With several tags on one commit that pick is arbitrary; it returned 2.0.256, bumped to 2.0.257, and that release already existed. This is structural rather than a one-off: update-v2-tag force-moves v2 onto every release commit, so the newest release commit always carries a second tag.

A second bug hid the first: with no set -e, the rejected git tag / git push still exited 0 and exported NEW_TAG=2.0.257 anyway, so the step went green and the failure surfaced two steps later as a confusing 422.

Nothing to do with #566 — any push touching src/, dist/, scripts/, package*.json or action.yml would have failed the same way.

Change

• Select the highest version tag by version order (git tag -l '[0-9]*.[0-9]*.[0-9]*' | sort -V | tail -1) instead of by tagged commit. The glob also keeps the legacy v-prefixed tags (v2, v1.111, v2-lite) out of the running, which removes the v-stripping branch that would have turned v1.111 into 1.111.1.
• set -eo pipefail so a rejected tag or push fails the step where it breaks.
• Guard against an empty tag list, and quote the variables.

Verification

Reproduced the three-tags-on-one-commit state in a scratch repo:

	result
old logic	0.1.0 — arbitrary pick, confirming the ambiguity
new logic	2.0.257 → next tag 2.0.258

bash -n clean.

Note

The failed run died before npm run update-v2-tag, so v2 still points at f6ecd22 — the payload change from #566 is on develop but not yet live for @v2 consumers. Merging this with auto-deploy cuts 2.0.258 and moves v2 forward, which ships it.

🤖 Generated with Claude Code

✨ PR Description

Purpose: Fix release tag selection to use semantic version ordering instead of commit recency, preventing incorrect version increments.

Main changes:

• Replace git describe with git tag -l and sort -V for version-based tag selection instead of commit-based
• Add error handling with set -eo pipefail and validation check for missing tags
• Quote variables and restore GitHub Actions output statements with proper escaping

Changelog

✨ New Features

• Support oversized payloads via server-side stashing
• Handle gzip-compressed payloads to reduce transmission size

🔧 Improvements

• Simplified payload parsing with centralized resolution logic
• Replaced repetitive JSON double-decoding with cleaner step outputs

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how}

[orca-security-us]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Infrastructure as Code	0   0   0   0	View in Orca
Passed	OSS Licenses	0   0   0   0	View in Orca
Passed	SAST	0   0   0   0	View in Orca
Passed	Secrets	0   0   0   0	View in Orca
Passed	Vulnerabilities	0   0   0   0	View in Orca

[linearb]

✨ PR Review

LGTM

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Review using Guidelines Learn how}

[MishaKav]

LGTM

[Copilot]

Pull request overview

This PR hardens the release-tagging script to select the next release tag based on semantic version ordering (rather than “newest tagged commit”), and to fail fast when tag creation/push fails—preventing accidental re-use of an existing release tag.

Changes:

• Switch latest-version detection from git describe on the newest tagged commit to version-based selection from the tag list.
• Add set -eo pipefail and a guard for an empty tag list so failures surface at the correct step.
• Quote tag/output variables and force-refresh tags from the remote.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.