From 3ba46f9d496e738659178a3ff0da640ed9dc0fb3 Mon Sep 17 00:00:00 2001 From: Keith Smith Date: Sat, 31 Oct 2026 01:52:09 -0600 Subject: [PATCH] Match upgrade.sh's example tag to the actual v.. format MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The "no tags found" error suggested git tag v1.0.0, which doesn't match how this project's tags are actually named — generates today's date into the example instead. No behavior change: git tag --sort=-creatordate already sorts by actual tag creation time regardless of the tag name's format, so the date-based scheme worked with the existing logic already. Co-Authored-By: Claude Sonnet 5 --- scripts/upgrade.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/upgrade.sh b/scripts/upgrade.sh index b704108..9f01bef 100755 --- a/scripts/upgrade.sh +++ b/scripts/upgrade.sh @@ -50,7 +50,7 @@ sudo -u "$EVECTION_USER" -H git fetch --tags --force LATEST_TAG="$(sudo -u "$EVECTION_USER" -H git tag --sort=-creatordate | head -n1)" if [ -z "$LATEST_TAG" ]; then echo "No tags found in this repo — nothing to deploy." \ - "Cut and push a release tag first (e.g. git tag v1.0.0 && git push --tags)." >&2 + "Cut and push a release tag first (e.g. git tag v$(date +%Y.%m.%d) && git push --tags)." >&2 exit 1 fi CURRENT_REF="$(sudo -u "$EVECTION_USER" -H git describe --tags --exact-match 2>/dev/null || echo "none")"