Skip to content

Adopt template-rust-cli CI and build conventions - #3

Merged
alshdavid merged 1 commit into
mainfrom
agent/deepseek-2-medium/948776a04af7
Nov 11, 2026
Merged

alshdavid merged 1 commit into
mainfrom
agent/deepseek-2-medium/948776a04af7

Conversation

@alshdavid-machine

Copy link
Copy Markdown

Closes ALSH-440.

Brings CI and the build setup in line with the template-rust-cli pattern.

Changes

  • Workflows: replace the custom main.yaml / pull-request.yaml with the template's pull_request.yaml, release.yaml and update_dependencies.yaml. Release now auto-increments the version, builds linux amd64/arm64 (musl), macOS arm64 and windows amd64/arm64, and publishes a GitHub release.
  • just removed: justfile deleted; CI invokes cargo directly.
  • .cargo customisation removed: .cargo/config.toml (target-dir = "target/.cargo") and the .github/install-scripts submodule are gone.
  • Cargo.toml: release profile optimisations (lto = "fat", codegen-units = 1, opt-level = 3, strip = true, panic = "abort"), the template's lint configuration, and package metadata.

Code changes required by the new lint job

The template denies clippy::pedantic + cargo lints, so the existing code needed a few fixes (no behaviour change intended): unwrap() in path/duration parsing replaced with error propagation, checked Duration subtraction, documented casts, and ownership passed into the writer thread.

Verification (local)

  • cargo clippy --all-targets --workspace -- -D warnings passes
  • cargo xfmt --check passes
  • cargo build --release + smoke run of procmon passes

- Replace custom workflows with the template's pull_request, release and
  update_dependencies workflows
- Remove justfile, .cargo config and the install-scripts submodule
- Add lint configuration and release profile optimisations to Cargo.toml
@alshdavid
alshdavid merged commit 8d17943 into main Nov 11, 2026
6 checks passed
@alshdavid
alshdavid deleted the agent/deepseek-2-medium/948776a04af7 branch November 11, 2026 05:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants