Gitfed
bastien-mrq/gitfed/ Commits/ 2d40944

Fix the go install instructions; tag releases going forward

Testing the exact command documented in 1.2.6 against the live instance surfaced two real problems: - The plain command tries proxy.golang.org first, which can't/won't resolve a self-hosted module — needs GOPRIVATE set (the standard Go mechanism for exactly this case, skips both the public proxy and the checksum database for matching paths). - @main doesn't reliably resolve either (hit a stale/conflicting pseudo-version once GOPRIVATE was set) — @latest backed by a real semver tag works cleanly and is the more idiomatic choice anyway. deploy/update.sh now tags the final "Deploy vX.Y.Z" commit on every release, so @latest keeps resolving to something going forward instead of erroring "no matching versions" the way it did until this release's v1.2.7 tag (pushed manually this once to unblock testing).

bastien-mrq 2026-07-29 12:15 commit 2d4094420e17c65a320c41b335eaf8d8ce998d42 parent 5241dbae6a763e041d434db56ecc7271e965bf2f
2 files changed +14 −3
M FEDERATION.md +6 −1
M deploy/update.sh +8 −2
FEDERATION.md
diff --git a/FEDERATION.md b/FEDERATION.md index 398b955..45a4083 100644 --- a/FEDERATION.md +++ b/FEDERATION.md @@ -65,9 +65,14 @@ ou le certificat présenté compte. Thomas installe l'outil de renouvellement (build direct, sans cloner le dépôt) : ```sh -go install git.neuromancer.ovh/bastien-mrq/gitfed/cmd/gitfed-renew-cert@main +GOPRIVATE=git.neuromancer.ovh/* go install git.neuromancer.ovh/bastien-mrq/gitfed/cmd/gitfed-renew-cert@latest ``` +`GOPRIVATE` dit à l'outil `go` de sauter le proxy public +(`proxy.golang.org`) et la base de sommes de contrôle pour ce chemin — +nécessaire pour tout module auto-hébergé, pas seulement celui-ci. Pour ne +plus avoir à le préciser à chaque fois : `go env -w GOPRIVATE=git.neuromancer.ovh/*`. + Puis récupère la clé d'hôte de **sa propre** instance et demande un premier certificat :
deploy/update.sh
diff --git a/deploy/update.sh b/deploy/update.sh index 080bb97..951f5eb 100755 --- a/deploy/update.sh +++ b/deploy/update.sh @@ -12,7 +12,12 @@ # # Add the new version's entry to CHANGELOG.md yourself before running this # — the script won't guess what changed. It commits the VERSION bump (and -# CHANGELOG.md, if you've staged it) as "Release vX.Y.Z". +# CHANGELOG.md, if you've staged it) as "Release vX.Y.Z", and tags the +# final "Deploy vX.Y.Z" commit "vX.Y.Z" — that tag is what makes +# `go install .../gitfed/cmd/<tool>@latest` resolve to something instead +# of erroring "no matching versions" (see FEDERATION.md). Nothing here +# pushes to the remote, including the tag — that's still a separate +# `git push vps main --tags` afterward, same as always. set -euo pipefail cd "$(dirname "${BASH_SOURCE[0]}")/.." @@ -67,5 +72,6 @@ ssh "$VPS_HOST" "kubectl -n $NAMESPACE apply -f $VPS_SRC_DIR/deploy/k8s/deployme git add deploy/k8s/deployment.yaml git commit -m "Deploy v$new_version" +git tag "v$new_version" -echo "==> done: v$new_version is live" +echo "==> done: v$new_version is live (tagged v$new_version — push with: git push vps main --tags)"