fix(version): look up the monthly tag without the v prefix

[mmmarinho]

What this does

Fixes the rolling-version computation so the libmarinholab-sas-core .deb (and the CMake package version) actually track main instead of staying pinned at 26.09.00.

Problem

tools/version.sh looks up the monthly version tag as v${YY.MM} (e.g. v26.09), but the project's tags are bare (26.09):

• The only tag in the repo is 26.09 (annotated → d488bb68), no v prefix.
• The bare name is also the convention sas_py relies on: its setuptools-git-versioning uses dev_template = "{tag}.{ccount}", which is why PyPI shows 26.9.4/26.9.5 from tag 26.09.

Because refs/tags/v26.09 never exists, NN was always 0 → version.sh always returned 26.09.00, so:

• tools/bump-changelog.sh never bumped debian/changelog (idempotent no-op),
• the .deb version stayed 26.09.00 while the branch content moved,
• cmake/GetVersion.cmake (which runs tools/version.sh) reported the same stale version.

With 5 commits after 26.09 on main, the version should have been 26.09.05.

Fix

tools/version.sh now looks up the monthly tag as YY.MM first, vYY.MM as a fallback — accepting either naming, preferring the project's actual (bare) convention. No tag renaming (renaming to v26.09 would break sas_py's PyPI versioning, which expects the bare tag).

find_version_tag() {
    local t
    for t in "${YYMM}" "v${YYMM}"; do
        if git rev-parse --verify "refs/tags/${t}" >/dev/null 2>&1; then
            printf '%s\n' "${t}"
            return 0
        fi
    done
    return 1
}

Single-file change (tools/version.sh); all consumers — bump-changelog.sh, cmake/GetVersion.cmake, docker/build.sh — funnel through it, so they all benefit with no changes of their own.

Verification

• bash tools/version.sh on a clone of main (5 commits after 26.09): 26.09.05 (previously 26.09.00).
• No monthly tag present → 26.09.00 (unchanged safe behavior).
• Only v26.09 present → 26.09.05 (fallback works).
• tools/bump-changelog.sh consumes the same version.sh output, so debian/changelog will now be stamped 26.09.05 before dpkg-buildpackage (the dch step is exercised in the sas_cpp docker env / SmartArmStack/smart_arm_stack_ROS2 PR fix(version): look up the monthly tag without the v prefix #5, where devscripts is installed).

Effect

• The PPA build in SmartArmStack/smart_arm_stack_ROS2 PR fix(version): look up the monthly tag without the v prefix #5 (which runs tools/bump-changelog.sh + dpkg-buildpackage) will now produce libmarinholab-sas-core_26.09.NN, so the PPA version moves with main — no more "static version, moving content" caveat.
• SmartArmStack/sas_core PR Accept a dqrobotics::dqrobotics target from a parent project #12's in-image build (pinned at tag 26.09) is unaffected: at the tag, NN = 0 → 26.09.00 exactly as before.

---

This pull request was created by an AI agent (OpenHands) on behalf of the repository owner.

[mmmarinho]

👍