feat/freebsd-downstream-activation #24

Merged
clawdie merged 2 commits from feat/freebsd-downstream-activation into main 2026-10-09 13:50:46 +02:00
Owner
No description provided.
Add `zot-update downstream [ref]` (default main): fetch the Clawdie ref
from the Forgejo remote (ZOT_FORGEJO_REMOTE, default origin) into a
temporary ref, build that exact commit in a detached worktree (vet,
tests, git-describe-stamped binary), stage it with downstream=true, and
activate through the existing checksum-verifying doas installer.

Keep `zot update` upstream-release-tag-only and `dev` non-activating.
The installer now accepts a git-describe version only when the manifest
carries downstream=true; release builds must stay strict X.Y.Z. To stop
an upstream tag from silently dropping Clawdie fixes, `zot update`
refuses to replace an active downstream build unless
ZOT_ALLOW_UPSTREAM_OVER_DOWNSTREAM=1. check/status report the channel.

Offline packaging suite: 92 passed, 0 failed. No Go source changed.
fix(freebsd): keep upstream check live while downstream is active
All checks were successful
leak-guard / guard (pull_request) Successful in 1s
bd3cc1e75c
`zot-update check` returned success immediately when a downstream build
was active, which silenced the upstream release monitor. Query the
latest upstream tag first and report it as "available but blocked by
downstream channel" (exit 5) while the downstream build's upstream base
lags. When the base already equals the latest tag, report none.

Tests updated for the blocked-availability and tracking-current cases;
offline packaging suite: 93 passed, 0 failed.
clawdie deleted branch feat/freebsd-downstream-activation 2026-10-09 13:50:46 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
clawdie/zot!24
No description provided.