Tag releases with the suite's numbers: v27.1-rc.1 #36

Merged
jcoffey-dev merged 1 commits from release/version-27.1-rc.1 into main 2026-10-28 16:57:26 +00:00
Owner

Moves the installer to the suite's release numbers for the 27.1 rc.1 gate: v27.1 for a series, v27.1.3 for a patch, v27.1-rc.1 for a release candidate.

  • scripts/build-release.sh accepts those tags, and still the dated ones so an old release can be rebuilt. A v27.1-rc.1 build reports 27.1-rc.1 from inbuxa version.
  • release.yml publishes an RC as a pre-release, so releases/latest, and the README's download, stay on the last final release.
  • Bug fix: the host server counted as the pinned release whenever its --version contained the pin. A 27.1 pin would have accepted 27.1-rc.1, 27.1.3 or 27.10.2, skipping the download or taking the wrong binary. It is now an exact match on the first word (the server prints only its version). New test: TestIsVersion.
  • The e2e host check (install-host.sh) accepts a two-digit year.
  • RC opt-in: an RC installer pins the suite's RCs, and a final installer pins only finals. That rule is written down in internal/release/release.go. Pins don't change here; the RC pins go in on tag day, once the RC artifacts and their checksums exist.

Checks: gofmt, go vet (amd64 and arm64), go test ./..., and build-release.sh with good and bad tags.

Moves the installer to the suite's release numbers for the 27.1 rc.1 gate: `v27.1` for a series, `v27.1.3` for a patch, `v27.1-rc.1` for a release candidate. - `scripts/build-release.sh` accepts those tags, and still the dated ones so an old release can be rebuilt. A `v27.1-rc.1` build reports `27.1-rc.1` from `inbuxa version`. - `release.yml` publishes an RC as a pre-release, so `releases/latest`, and the README's download, stay on the last final release. - **Bug fix:** the host server counted as the pinned release whenever its `--version` *contained* the pin. A 27.1 pin would have accepted 27.1-rc.1, 27.1.3 or 27.10.2, skipping the download or taking the wrong binary. It is now an exact match on the first word (the server prints only its version). New test: `TestIsVersion`. - The e2e host check (`install-host.sh`) accepts a two-digit year. - RC opt-in: an RC installer pins the suite's RCs, and a final installer pins only finals. That rule is written down in `internal/release/release.go`. Pins don't change here; the RC pins go in on tag day, once the RC artifacts and their checksums exist. Checks: gofmt, `go vet` (amd64 and arm64), `go test ./...`, and `build-release.sh` with good and bad tags.
jcoffey-dev added 1 commit 2026-10-28 16:55:07 +00:00
Tag releases with the suite's numbers: v27.1-rc.1
ci / test (pull_request) Successful in 1m25s
a7de7a517d
The installer joins the INBUXA suite's release numbers: v27.1 for a series,
v27.1.3 for a patch, v27.1-rc.1 for a release candidate.

- build-release.sh accepts those tags, and still the dated ones, so an
  old release can be rebuilt.
- release.yml publishes a release candidate as a pre-release, so
  releases/latest stays on the last final release.
- The host server counts as the pinned release only when its --version
  is exactly the pin. The substring match took 27.1-rc.1, 27.1.3 and
  27.10.2 for 27.1, so a host install would have skipped the download
  or accepted the wrong binary.
- The e2e host check accepts a two-digit year.
- release.go says how RCs are opted into: an RC installer pins RCs, and
  a final installer pins finals.

Claude-Session: https://claude.ai/code/session_01Y2F7CWRXorttf5sjSbxwpj
jcoffey-dev force-pushed release/version-27.1-rc.1 from d87a3745ac to a7de7a517d 2026-10-28 16:55:07 +00:00 Compare
jcoffey-dev merged commit 700ae5d4aa into main 2026-10-28 16:57:26 +00:00
jcoffey-dev deleted branch release/version-27.1-rc.1 2026-10-28 16:57:26 +00:00
Sign in to join this conversation.