mod-signal 0.9.1

Unified OS signal handling for Rust. SIGTERM / SIGINT / SIGHUP / SIGPIPE and Windows equivalents through one API. Graceful shutdown orchestration with priority ordering, timeout enforcement, and hook chaining. Replaces the patchwork of ctrlc + signal-hook with a clean runtime-agnostic substrate.
Documentation
name: CI

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

env:
  CARGO_TERM_COLOR: always

jobs:
  test:
    name: Test (${{ matrix.os }})
    runs-on: ${{ matrix.os }}
    strategy:
      fail-fast: false
      matrix:
        os: [ubuntu-latest, macos-latest, windows-latest]
    steps:
      - uses: actions/checkout@v5
      - uses: dtolnay/rust-toolchain@stable
      - uses: Swatinem/rust-cache@v2

      - name: Build (default features)
        run: cargo build --verbose
      - name: Test (default features)
        run: cargo test --verbose

      - name: Build (no default features)
        run: cargo build --no-default-features --verbose

      - name: Build (all features)
        run: cargo build --all-features --verbose
      - name: Test (all features)
        run: cargo test --all-features --verbose

  clippy:
    name: Clippy
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: dtolnay/rust-toolchain@stable
        with:
          components: clippy
      - uses: Swatinem/rust-cache@v2
      - name: Clippy (all features)
        run: cargo clippy --all-targets --all-features -- -D warnings
      - name: Clippy (no default features)
        run: cargo clippy --all-targets --no-default-features -- -D warnings

  fmt:
    name: Rustfmt
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: dtolnay/rust-toolchain@stable
        with:
          components: rustfmt
      - run: cargo fmt --all -- --check

  docs:
    name: Doc build
    runs-on: ubuntu-latest
    env:
      RUSTDOCFLAGS: "-D warnings"
    steps:
      - uses: actions/checkout@v5
      - uses: dtolnay/rust-toolchain@stable
      - uses: Swatinem/rust-cache@v2
      - run: cargo doc --all-features --no-deps

  msrv:
    name: MSRV (Rust 1.75)
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: dtolnay/rust-toolchain@1.75
      - uses: Swatinem/rust-cache@v2

      # Regenerate Cargo.lock so transitive resolution starts from
      # the current crates.io index. Then pin transitive deps that
      # have raised their MSRV above ours.
      - name: Delete existing Cargo.lock
        run: rm -f Cargo.lock

      - name: Regenerate Cargo.lock with MSRV
        run: cargo generate-lockfile

      # Cargo 1.75 lacks the MSRV-aware resolver (stabilized in 1.84),
      # so newly published versions can break the regenerated lockfile.
      # `async-lock 3.4.x` raised its MSRV to 1.85 in early 2026; it
      # only appears when the `async-std` feature is enabled, which is
      # excluded from MSRV coverage below, but we pin defensively in
      # case the resolver pulls it in via another optional path.
      # Drop these pins when MSRV is raised.
      - name: Pin MSRV-incompatible transitive deps
        run: |
          cargo update -p async-lock@3.4.2 --precise 3.3.0 || true

      # MSRV is validated against the minimum realistic feature set
      # (the `tokio` default plus `ctrlc-fallback`). The `async-std`
      # feature pulls in `async-lock`, `polling`, and `rustix` versions
      # that have raised their MSRV beyond 1.75 and is excluded from
      # MSRV coverage; consumers who need `async-std` should pin their
      # own toolchain to a newer minor.
      - name: Check MSRV compatibility (lib, no default features)
        run: cargo check --lib --no-default-features --features "std"

      - name: Check MSRV compatibility (lib, default features)
        run: cargo check --lib

      - name: Check MSRV compatibility (lib, default + ctrlc-fallback)
        run: cargo check --lib --features "ctrlc-fallback"