fix(ci): move check job to OpenSUSE runner + lint posture cleanup #5
No reviewers
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
psa-systems/bunyip!5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/ci-check-runner"
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?
Two problems landed together when the SSO/full-dev merge hit main:
actions/checkout@v5failed with "node: executable file not found" inside the rust:1-slim-trixie container. The slim rust image does not ship Node.js, which checkout@v5's JS runtime needs. Swap the check job to the same${{ vars.RUNS_ON_OPENSUSE_BASE_LATEST }}runner the build-images job already uses (rust + node baked in), and rewrite the steps to mirror the pre-commit recipe: cargo check / clippy / fmt on the native workspace (excluding bunyip-web), then a second pass on bunyip-web with --target wasm32-unknown-unknown.cargo clippy ... -- -D warningsflipped a long tail of advisory clippy nits and post-merge dead_code orphans into hard errors. Applycargo clippy --fixfor the auto-fixable lints, then add[lints.rust]/[lints.clippy]allows in bunyip-web/Cargo.toml for the cosmetic categories (doc_lazy_continuation, enum_variant_names) and the transitionaldead_code/unused_*/deprecatedbuckets. Same posture as the drillmark + mokosh-server lint cleanups.Co-Authored-By: Claude Opus 4.7 noreply@anthropic.com
Two problems landed together when the SSO/full-dev merge hit main: 1. `actions/checkout@v5` failed with "node: executable file not found" inside the rust:1-slim-trixie container. The slim rust image does not ship Node.js, which checkout@v5's JS runtime needs. Swap the check job to the same `${{ vars.RUNS_ON_OPENSUSE_BASE_LATEST }}` runner the build-images job already uses (rust + node baked in), and rewrite the steps to mirror the pre-commit recipe: cargo check / clippy / fmt on the native workspace (excluding bunyip-web), then a second pass on bunyip-web with --target wasm32-unknown-unknown. 2. `cargo clippy ... -- -D warnings` flipped a long tail of advisory clippy nits and post-merge dead_code orphans into hard errors. Apply `cargo clippy --fix` for the auto-fixable lints, then add `[lints.rust]` / `[lints.clippy]` allows in bunyip-web/Cargo.toml for the cosmetic categories (doc_lazy_continuation, enum_variant_names) and the transitional `dead_code` / `unused_*` / `deprecated` buckets. Same posture as the drillmark + mokosh-server lint cleanups. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>bunyip-web's main.rs has `asset!("/assets/styles.css")`, which dioxus' macro resolves at compile time. The file is a gitignored Tailwind build artifact (see .gitignore line for bunyip-web/assets/styles.css), so a clean CI checkout doesn't have it, and cargo check fails before any clippy/test step runs. This workflow only compile-validates and never renders CSS, so an empty file is sufficient. The real Tailwind build stays in bunyip-web/oci-build/Dockerfile for deployment images. Same fix pattern mokosh-clients applied in 964f092. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>