shipping-rust-binaries-with-goreleaser #63

Activity

1. github-actions

   assigned

   dezren39

   on Nov 7, 2023
2. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   on Oct 29, 2026
3. dezren39 commented on Oct 29, 2026

   

   dezren39

   on Oct 29, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done

   • Agent: queue worker (repo-worker-code, lane B)
   • Session / ID: queue task 2007 (triage)
   • Found via: queue claim
   • Task: Triage verdict: NOT CONFIRMED as an actionable problem — closing as not planned / superseded.
   • Expectation: done = verdict backed by current-main evidence (below); no follow-up fix packet, per reasoning.

   Evidence at main 2953f274 (verified 2026-10-29T00:49:02Z):

   • The issue (filed 2023-11-07) is two reference links only — the jondot "Shipping Rust binaries with GoReleaser" article and mre/cargo-deliver — with no named binary, no problem statement, and no acceptance criteria. Zero comments since filing.
   • GoReleaser is already adopted where this repo has a shippable binary: root .goreleaser.yaml + .github/workflows/goreleaser.yml (tag-triggered, manual snapshot runs) — but it builds the Go binary graph from sources/graph. No Rust build is configured, and cargo-deliver appears nowhere in the tree (code search: 0 hits).
   • There is no root Rust binary to ship: root Cargo.toml is a stub (code 0.1.0, no dependencies) whose declared [[bin]] path .src/main.rs does not exist (404 at HEAD).
   • The Rust code under pkgs/ is experiments/examples (hello-*, pavex vendoring, web-gen-api spikes) in a Nix-first repo — built via Nix where built at all, not release artifacts with consumers.

   So there is nothing concrete to route: no Rust release binary exists, and inventing one to satisfy a link-only 2023 note would be manufactured work. If a real Rust binary in this repo later needs release distribution, file a new issue naming the binary and its consumers — GoReleaser (already in-tree for Go) is the obvious starting point.
4. dezren39

   closed this as not plannedon Oct 29, 2026
5. dezren39

   removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   on Oct 29, 2026
6. developing-today

   added

   status:done

   on Oct 29, 2026
7. developing-today

   closed this as completedon Oct 29, 2026