Set up action to build compiled binaries on release #48

New issue

Closed

opened 2026-07-07 23:46:01 +00:00 by javif89 · 0 comments

javif89 commented

2026-07-07 23:46:01 +00:00

Owner

In the future, I want to set up better nix packaging. One of those pieces is the user not having to recompile waycast on every update.

We should have an action that compiles binaries for the target systems on every release, and attaches those artifacts to the release. This is common practice in most software projects.

Tools to check out for this purpose:

Cargo release (bump version + generate commands + commit back to master)
Cargo dist (build binaries)

In the future, I want to set up better nix packaging. One of those pieces is the user not having to recompile waycast on every update. We should have an action that compiles binaries for the target systems on every release, and attaches those artifacts to the release. This is common practice in most software projects. Tools to check out for this purpose: - Cargo release (bump version + generate commands + commit back to master) - Cargo dist (build binaries)

javif89 added the

packaging

CI/CD

labels

2026-07-07 23:46:01 +00:00

javif89 referenced this issue

2026-07-07 23:54:59 +00:00

Binary caching #29

javif89 added this to the Infrastructure project

2026-07-08 00:21:40 +00:00

javif89 self-assigned this

2026-07-08 03:55:00 +00:00