Gitfed
bastien-mrq/gitfed/ Commits/ 93ed5a2

Release v1.2.8

bastien-mrq 2026-07-29 15:12 commit 93ed5a2555f047d61d3239099ec2bcca4dafb9fb parent deeebe21250215a02fdda329edf806420edc4c3c
2 files changed +5 −1
M CHANGELOG.md +4 −0
M VERSION +1 −1
CHANGELOG.md
diff --git a/CHANGELOG.md b/CHANGELOG.md index 1d485aa..91514ee 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,10 @@ A bullet starting with `**BREAKING:**` flags a change gitfed-ctl's update wizard makes you acknowledge individually before it will let you upgrade past that version. +## 1.2.8 + +- New `gitfed-ctl`: an update utility for instances that follow someone else's releases rather than cutting their own. Runs locally on the VPS (no SSH-to-self, no repeated password prompt — the problem with `deploy/update.sh current` observed live), checks for new versions, makes any `**BREAKING:**` CHANGELOG.md entry something you have to individually acknowledge before continuing, optionally backs up the data volume, then rebuilds and redeploys. `GOPRIVATE=git.neuromancer.ovh/* go install git.neuromancer.ovh/bastien-mrq/gitfed/cmd/gitfed-ctl@latest`, then `sudo gitfed-ctl` from inside a checkout. Account and federation-trust management stay on the web admin UI, which already covers both. + ## 1.2.7 - Fixed the `go install` instructions from 1.2.6: `@main` doesn't reliably resolve (Go's module resolution wants a real semver tag, not a branch pseudo-version, for this kind of self-hosted lookup), and the plain command errors out by default anyway since `go` tries the public proxy first. The real, tested command is `GOPRIVATE=git.neuromancer.ovh/* go install .../gitfed/cmd/gitfed-renew-cert@latest`. `deploy/update.sh` now also tags every release (`vX.Y.Z`) so `@latest` keeps resolving to something going forward — this release is the first one tagged.
VERSION
diff --git a/VERSION b/VERSION index c04c650..db6fb4a 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -1.2.7 +1.2.8