armature-queue 0.7.0

Job queue and background processing for Armature
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77

name: Test

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

permissions:
  contents: read

env:
  CARGO_TERM_COLOR: always

jobs:
  test:
    name: test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 # v5
      # `armature-testkit` is `publish = false`, so this crate's dev-dependency on
      # it cannot come from the registry. It is the one sibling that still has to
      # be present on disk; everything else resolves from crates.io.
        with:
          persist-credentials: false
      - uses: actions/checkout@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 # v5
        with:
          repository: quinnjr/armature-testkit
          # Pinned: without a ref this takes whatever the default branch holds
          # at the moment the job starts, which made four repos fail when their
          # workflows ran before testkit's own push had landed.
          ref: develop
          path: armature-testkit
          persist-credentials: false
      - name: Move the checkout beside this crate
        run: |
          mkdir -p ../armature-testkit
          cp -r armature-testkit/. ../armature-testkit/
          rm -rf armature-testkit
      - uses: dtolnay/rust-toolchain@683b588c487a69d01f6c6ddf40f036ff682cc2c8 # master
        with:
          toolchain: stable
      - uses: Swatinem/rust-cache@6323deb102c322ba6fcbdcafc7e3dddab59af2b6 # v2
      - run: cargo test --all-features

  msrv:
    name: MSRV 1.94.1
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 # v5
      # `armature-testkit` is `publish = false`, so this crate's dev-dependency on
      # it cannot come from the registry. It is the one sibling that still has to
      # be present on disk; everything else resolves from crates.io.
        with:
          persist-credentials: false
      - uses: actions/checkout@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 # v5
        with:
          repository: quinnjr/armature-testkit
          # Pinned: without a ref this takes whatever the default branch holds
          # at the moment the job starts, which made four repos fail when their
          # workflows ran before testkit's own push had landed.
          ref: develop
          path: armature-testkit
          persist-credentials: false
      - name: Move the checkout beside this crate
        run: |
          mkdir -p ../armature-testkit
          cp -r armature-testkit/. ../armature-testkit/
          rm -rf armature-testkit
      - uses: dtolnay/rust-toolchain@683b588c487a69d01f6c6ddf40f036ff682cc2c8 # master
        with:
          toolchain: 1.94.1
      - uses: Swatinem/rust-cache@6323deb102c322ba6fcbdcafc7e3dddab59af2b6 # v2
        with:
          key: msrv
      # `--all-targets` without `--all-features`: the MSRV claim is about the
      # crate as published with its defaults, not about every optional feature.
      - run: cargo check --all-targets