Release 2.3.0.0202: version-tagged images, changelog
continuous-integration/drone/push Build is passing

- Drone: an image-tags step writes .tags (latest, commit SHA, changelog
  version) for the master publish, so each release can be pulled and
  rolled back by version. The master publish step no longer hardcodes tags.
- Version 2.2.0.0201 -> 2.3.0.0202 in xteve.go and changelog-beta.md, with
  a changelog entry covering the improvements branch.
- README / README-DEV describe the version tag.
This commit is contained in:
nathan committed 2026-10-02 10:54:29 +10:00
1 parent e1a6956657
commit d385e68b31
6 files changed
+37 -7

No files matched your search

+1 -1
View File
@@ -74,7 +74,7 @@ registry.coadcorp.com/nathan/xteve
Tags:
* `latest` and `<commit sha>` from the `master` branch.
* `latest`, the release version (for example `2.3.0.0202`) and `<commit sha>` from the `master` branch. Pin the version tag if you want to control when you upgrade, or to roll back.
* `<branch name>` and `<commit sha>` from every other branch.
```bash