Private
Public Access
Document the release tag format: v<year>.<month>.<day>, then .2, .3
The docs and upgrade.sh's hint showed zero-padded `date +%Y.%m.%d` and said nothing about a second release in a day. Tags are unpadded (v2026.11.1) with .2, .3, ... appended for each further release that day. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
ac5e951749
commit
fed5bcc49e
2 files changed
+5
-4
No files matched your search
+4
-3
@@ -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
|
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
|
as the author's other self-hosted projects. A release tag looks like
|
||||||
`v2026.10.31` (`v<year>.<month>.<day>`); `scripts/install.sh` and
|
`v2026.11.1` (`v<year>.<month>.<day>`, 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
|
`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
|
time, via a detached-HEAD checkout, regardless of what's checked out or
|
||||||
committed on `main`.
|
committed on `main`.
|
||||||
@@ -28,7 +29,7 @@ Before your first production install, cut and push a tag from whatever commit
|
|||||||
you want to ship:
|
you want to ship:
|
||||||
|
|
||||||
```bash
|
```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
|
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:
|
from — the next `upgrade.sh` run on the server picks it up:
|
||||||
|
|
||||||
```bash
|
```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
|
git push --tags
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|||||||
+1
-1
@@ -81,7 +81,7 @@ fi
|
|||||||
LATEST_TAG="$(git tag --sort=-creatordate | head -n1)"
|
LATEST_TAG="$(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 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
|
exit 1
|
||||||
fi
|
fi
|
||||||
CURRENT_REF="$(git describe --tags --exact-match 2>/dev/null || echo "none")"
|
CURRENT_REF="$(git describe --tags --exact-match 2>/dev/null || echo "none")"
|
||||||
|
|||||||
Reference in new issue
Block a user