diff --git a/docs/install.md b/docs/install.md index 9038ef5..844581c 100644 --- a/docs/install.md +++ b/docs/install.md @@ -19,7 +19,8 @@ Both SQLite and PostgreSQL are fully supported. Steps that differ are marked Evection is deployed from git tags, never from a branch tip — the same pattern as the author's other self-hosted projects. A release tag looks like -`v2026.10.31` (`v..`); `scripts/install.sh` and +`v2026.11.1` (`v..`, no zero padding); a second release the same +day is `v2026.11.1.2`, a third `v2026.11.1.3`, and so on. `scripts/install.sh` and `scripts/upgrade.sh` both always deploy whatever tag is newest by creation time, via a detached-HEAD checkout, regardless of what's checked out or committed on `main`. @@ -28,7 +29,7 @@ Before your first production install, cut and push a tag from whatever commit you want to ship: ```bash -git tag v$(date +%Y.%m.%d) +git tag v$(date +%Y.%-m.%-d) # a later release the same day: append .2, .3, ... git push --tags ``` @@ -427,7 +428,7 @@ To ship a new release, just cut and push a new tag on the machine you build from — the next `upgrade.sh` run on the server picks it up: ```bash -git tag v$(date +%Y.%m.%d) +git tag v$(date +%Y.%-m.%-d) # a later release the same day: v2026.11.1.2, .3, ... git push --tags ``` diff --git a/scripts/upgrade.sh b/scripts/upgrade.sh index 13d3466..96e119c 100755 --- a/scripts/upgrade.sh +++ b/scripts/upgrade.sh @@ -81,7 +81,7 @@ fi LATEST_TAG="$(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 v$(date +%Y.%m.%d) && 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="$(git describe --tags --exact-match 2>/dev/null || echo "none")"