A 27.1 installer "do-better": stop hand-tracking the pinned releases.
inbuxa upgrade --check prints the same "what is here → what this installer installs" table a dry run does, then stops with an exit code a script or cron job can act on:
10 — at least one component can be upgraded
0 — nothing can
It changes nothing, so it needs neither --yes nor root. It reuses the existing UpgradePlan (which reads the installed versions from the machine), so there's no new network call or source of truth — "a newer release" is simply what this installer pins.
inbuxa upgrade --check || notify-me # in a weekly cron job
cmd/inbuxa/main.go: a --check flag + a short report-and-stop branch; usage updated.
main_test.go: --check is accepted as an option (not taken for a component).
go build, go vet (amd64 + arm64), gofmt, go test ./..., and the stdlib-only check all pass locally. Independent of the other open PRs; branches off main.
Not merged; opening for review.
A 27.1 installer "do-better": stop hand-tracking the pinned releases.
`inbuxa upgrade --check` prints the same "what is here → what this installer installs" table a dry run does, then stops with an exit code a script or cron job can act on:
- **10** — at least one component can be upgraded
- **0** — nothing can
It changes nothing, so it needs neither `--yes` nor root. It reuses the existing `UpgradePlan` (which reads the installed versions from the machine), so there's no new network call or source of truth — "a newer release" is simply what this installer pins.
inbuxa upgrade --check || notify-me # in a weekly cron job
- `cmd/inbuxa/main.go`: a `--check` flag + a short report-and-stop branch; usage updated.
- `main_test.go`: `--check` is accepted as an option (not taken for a component).
`go build`, `go vet` (amd64 + arm64), `gofmt`, `go test ./...`, and the stdlib-only check all pass locally. Independent of the other open PRs; branches off `main`.
Not merged; opening for review.
inbuxa upgrade --check prints the same what-is-here against what-this-
installer-installs table as a dry run, then stops with an exit code a
script or cron job can act on: 10 when a component can be upgraded, 0
when none can. It changes nothing, so it needs neither --yes nor root.
This replaces hand-tracking the pinned releases with a command that says
when the installed suite is behind the one this installer ships.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A 27.1 installer "do-better": stop hand-tracking the pinned releases.
inbuxa upgrade --checkprints the same "what is here → what this installer installs" table a dry run does, then stops with an exit code a script or cron job can act on:It changes nothing, so it needs neither
--yesnor root. It reuses the existingUpgradePlan(which reads the installed versions from the machine), so there's no new network call or source of truth — "a newer release" is simply what this installer pins.cmd/inbuxa/main.go: a--checkflag + a short report-and-stop branch; usage updated.main_test.go:--checkis accepted as an option (not taken for a component).go build,go vet(amd64 + arm64),gofmt,go test ./..., and the stdlib-only check all pass locally. Independent of the other open PRs; branches offmain.Not merged; opening for review.
20fa6086afto19d54e9cf0