Prepare bakery distribution for breadboard CLI and desktop #62
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/bb-60-bakery-distribution"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Prepare separate breadboard-cli and breadboard-desktop client manifests plus dev, RC and stable workflows on the Hestia runner. The workflows build an exact origin commit, prepare immutable checksummed native artifacts, and regenerate the signed track index. They remain disabled until BREADBOARD_BAKERY_ENABLED is true and the documented signing-key path and runner prerequisites are provisioned.
Verified workspace build/tests/clippy, docs check, full npm build and Svelte check. Built the desktop deb headlessly with a dev version override and staged both real binaries with verified checksums. Syntax/manifest checks, invalid-version and overwrite rejection, and an isolated signed-index integration passed. The optional whole-repo fmt check reports existing formatting drift in unchanged Rust files; check.yml does not gate fmt.
Registry dependency: Breadway/bread-ecosystem#50 (ECO-48), merge before activation. The Hestia filesystem publisher does not need REGISTRY_TOKEN or a separate upload credential. No secret, live index, installed binary, personal config, release tag or desktop session was changed.
Refs #47 (BB-60).
Parent BB-60 implementation is prepared for review. Required check CI for head
ae1f01135bis queued at https://git.breadway.dev/Breadway/breadboard/actions/runs/47/jobs/0. Keeping this PR card in DOING until the configured check succeeds; any failed check will be commented and returned to TODO.The configured check CI is now green on the published head. Moving the PR card to REVIEW for independent review; live publishing/activation has not occurred.
Re-review: rework still required on PR #62
Acceptance interpretation: (1) publish separate CLI and desktop artifacts for the triggering source revision; (2) only advance both product versions and the signed track index as one recoverable publication; (3) require the registry dependency and keep live activation gated until credentials and runner setup are ready.
The manifests and three workflows cover the first criterion, and CI is green at
ae1f01135bb070656b633ec619cdec452633695e. The publication section atscripts/ci-bakery-release.sh:66-80still moves both version directories andlatestlinks before calling the shared signed index generator. Its lock only serializes breadboard publishers; another repository can regenerate the track index between these mutations. If index signing fails, the two latest links can point to artifacts missing from the signed index. The previous review's concurrency and failure requirement remains unmet.Keep PR #62 open and rework on
feature/bb-60-bakery-distribution. Do not open another PR for BB-60. Keep the workflows disabled until the transaction and activation prerequisites are ready.Updated submission received on PR #62 at
00cfdf8ce3c868227d0993145f08a61ba4affaef. Static review finds the staged full-track index, shared generator lock, rollback path, and isolated failure/concurrency regression address the prior publication race. The PR is mergeable, but its Forgejo check is still pending. Holding the card in DOING until CI completes, then I will post the final review verdict. No artifacts have been published.PR #62 rework now includes a staged full-track index, shared generator lock, rollback handling, and isolated concurrency/signing-failure regression coverage. Local checks pass; the exact-head Forgejo CI check was pending at last report. Moving implementation to REVIEW for the requested pipeline handoff. If CI fails, return to TODO with the failure recorded. No publication or live activation was performed.