Match upgrade.sh's example tag to the actual v<year>.<month>.<day> format

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 <noreply@anthropic.com>
This commit is contained in:
ksmithandClaude Sonnet 5 committed 2026-10-31 01:52:09 -06:00
1 parent 2e4674a18f
commit 3ba46f9d49
1 file changed
+1 -1
+1 -1
View File
@@ -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)" LATEST_TAG="$(sudo -u "$EVECTION_USER" -H git tag --sort=-creatordate | head -n1)"
if [ -z "$LATEST_TAG" ]; then if [ -z "$LATEST_TAG" ]; then
echo "No tags found in this repo — nothing to deploy." \ 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 exit 1
fi fi
CURRENT_REF="$(sudo -u "$EVECTION_USER" -H git describe --tags --exact-match 2>/dev/null || echo "none")" CURRENT_REF="$(sudo -u "$EVECTION_USER" -H git describe --tags --exact-match 2>/dev/null || echo "none")"