svccat 1.5.0

Detect drift between your declared service catalog and what actually lives in the repo.
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

name: Continuous Integration & Verification

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

jobs:
  test-and-verify:
    name: Verify Registry Deployment
    # This loops through 3 OS platforms × 3 Rust toolchains = 9 independent runners
    strategy:
      fail-fast: false # Ensures one failing job doesn't cancel the other 8 downloads
      matrix:
        os: [ubuntu-latest, windows-latest, macos-latest]
        rust: [stable, beta, nightly]

    runs-on: ${{ matrix.os }}

    steps:
      # 1. Bring down the repo code to let the runner know what to execute
      - name: Checkout Source Code
        uses: actions/checkout@v4

      # 2. Dynamically provision the specific matrix toolchain channel
      - name: Install Rust Toolchain
        uses: dtolnay/rust-toolchain@master
        with:
          toolchain: ${{ matrix.rust }}

      # 3. FORCE NETWORK HIT FROM CRATES.IO
      # This completely bypasses any local targets and pulls directly from the public registry.
      # Using --force ensures the runner downloads the crate assets on every single run.
      - name: Install Latest Release From Registry
        run: cargo install svccat --force --no-track

      # 4. Optional: Run your verification test suite against the installed binary
      - name: Verify CLI Execution
        run: svccat --version