ci: gitea workflow, drop inherited github workflows, embed commit in --version #10

Merged

grenade merged 2 commits from ci/gitea-workflows-and-build-sha into main 2026-09-03 10:02:40 +00:00

Conversation 0 Commits 2 Files Changed 9 +142 -495

grenade commented 2026-09-03 09:51:03 +00:00

Owner

Copy Link

First lair-only change on top of origin v4.0.2. Step 1 of #8; establishes the merge-conflict resolution rule in #1.

What changed

• Deleted .github/ (five workflows and the disk action). Gitea Actions also reads .github/workflows, so origin's GitHub-hosted jobs would queue forever for ubuntu-latest. On every origin-main merge the standing resolution is git rm -r .github/workflows.
• .gitea/workflows/ci.yml on the rust runner: fmt, clippy with -D warnings (same invocation as clippy.sh), build, test, doc, plus a check that the built binary's --version carries a commit. Origin's CPU benchmark job is not carried over; the GPU harness (#2) is the real gate.
• crates/miner-cli/build.rs embeds MINER_BUILD_SHA (env override, else git rev-parse with a -dirty marker, else unknown). --version now prints miner-cli 4.0.2 (<sha>). The deploy in #8 asserts the running binary is the commit it shipped; semver alone cannot.

Validation

Local, toolchain 1.93.0 per rust-toolchain:

cargo fmt --all -- --check                                  ok
cargo clippy --workspace --all-targets --all-features --locked -- -D warnings   ok
cargo test --locked --workspace                             all passing
./target/debug/quantus-miner --version                      miner-cli 4.0.2 (cb6deb91391a-dirty)
MINER_BUILD_SHA=deadbeef cargo build -p miner-cli           miner-cli 4.0.2 (deadbeef)

This PR is also the first run of the new workflow itself. If the ci checks do not appear on this PR, Actions is not enabled on the repo (the one thing not verifiable through the API).

Origin coupling

.gitea/ and build.rs are new files. main.rs gains one const and one attribute argument under a // lair: marker. lair/quantus's validate still matches on the 4.0.2 substring, so nothing downstream breaks before #8's deploy replaces it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5

First lair-only change on top of origin v4.0.2. Step 1 of #8; establishes the merge-conflict resolution rule in #1. ## What changed - **Deleted `.github/`** (five workflows and the `disk` action). Gitea Actions also reads `.github/workflows`, so origin's GitHub-hosted jobs would queue forever for `ubuntu-latest`. On every `origin-main` merge the standing resolution is `git rm -r .github/workflows`. - **`.gitea/workflows/ci.yml`** on the `rust` runner: fmt, clippy with `-D warnings` (same invocation as `clippy.sh`), build, test, doc, plus a check that the built binary's `--version` carries a commit. Origin's CPU benchmark job is not carried over; the GPU harness (#2) is the real gate. - **`crates/miner-cli/build.rs`** embeds `MINER_BUILD_SHA` (env override, else `git rev-parse` with a `-dirty` marker, else `unknown`). `--version` now prints `miner-cli 4.0.2 (<sha>)`. The deploy in #8 asserts the running binary is the commit it shipped; semver alone cannot. ## Validation Local, toolchain 1.93.0 per `rust-toolchain`: ``` cargo fmt --all -- --check ok cargo clippy --workspace --all-targets --all-features --locked -- -D warnings ok cargo test --locked --workspace all passing ./target/debug/quantus-miner --version miner-cli 4.0.2 (cb6deb91391a-dirty) MINER_BUILD_SHA=deadbeef cargo build -p miner-cli miner-cli 4.0.2 (deadbeef) ``` This PR is also the first run of the new workflow itself. If the `ci` checks do not appear on this PR, Actions is not enabled on the repo (the one thing not verifiable through the API). ## Origin coupling `.gitea/` and `build.rs` are new files. `main.rs` gains one `const` and one attribute argument under a `// lair:` marker. lair/quantus's validate still matches on the `4.0.2` substring, so nothing downstream breaks before #8's deploy replaces it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5

grenade added 1 commit 2026-09-03 09:51:04 +00:00

ci: gitea workflow, drop inherited github workflows, embed commit in --version ... 094536a341

First lair-only change on top of origin v4.0.2 (quantus/miner#8, #1).

- Delete .github/ (workflows and the disk action). Gitea Actions reads
  .github/workflows too, so origin's GitHub-hosted jobs would queue forever
  for runners that do not exist here. Standing resolution on every
  origin-main merge: `git rm -r .github/workflows`.
- Add .gitea/workflows/ci.yml on the `rust` runner: fmt, clippy with
  -D warnings (same invocation as clippy.sh), build, test, doc, and a check
  that the built binary reports a commit in --version.
- crates/miner-cli/build.rs embeds MINER_BUILD_SHA (env override, else
  git rev-parse with a -dirty marker, else "unknown") and --version prints
  "<semver> (<sha>)". A deploy that follows main needs to assert the running
  binary is the commit it shipped; the semver alone cannot do that.

Origin coupling: .gitea/ and build.rs are new files; main.rs gains one const
and one attribute argument behind a `// lair:` marker.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5

grenade added 1 commit 2026-09-03 09:54:33 +00:00

ci: add rustfmt and clippy components explicitly ... db6316713a

rustup auto-installs the pinned toolchain from rust-toolchain on the runner
but not its listed components; the fmt job failed with "cargo-fmt is not
installed for the toolchain". Add the component in the two jobs that need it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5

grenade referenced this pull request 2026-09-03 10:00:18 +00:00

bench: quantus-bench harness and a workflow that measures on a mining host #11

grenade merged commit 36ffbbadbf into main 2026-09-03 10:02:40 +00:00

grenade deleted branch ci/gitea-workflows-and-build-sha 2026-09-03 10:02:40 +00:00

grenade referenced this issue from a commit 2026-09-03 10:02:41 +00:00

Merge pull request 'ci: gitea workflow, drop inherited github workflows, embed commit in --version' (#10) from ci/gitea-workflows-and-build-sha into main

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

needs-benchmark

Gain is estimated, not measured; needs a run on a 5090 host

needs-chain

May require a matching change in quantus/chain

origin-coupling

Touches how the lair fork tracks Quantus-Network/quantus-miner

perf

Mining throughput workstream

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

grenade

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blackbeard/miner#10