beam_mcp/.github/workflows/conformance.yml at main · ScriptKittyOS/beam_mcp · GitHub

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
# SPDX-FileCopyrightText: 2026 Sudo Apt Holdings LLC
# SPDX-License-Identifier: Apache-2.0
#
# The conformance step, CI-ONLY by decision: the local gate (tools/gate.sh, fifteen steps)
# stays dependency-light so a contributor with Elixir and Erlang runs it green without a Node
# toolchain or a Python interpreter, and stays the gate people actually run. This job carries
# the second toolchain the number costs -- Node 22, pinned -- and the runner's python3, runs
# tools/conformance.sh with the suite pinned by exact version, and fails on a regression
# against conformance/baseline-<revision>.yml or a stale entry, by the suite's own exit code.
#
# IT FAILS LOUDLY, NEVER SKIPS: tools/conformance.sh exits 2 by name when node >= 22 or python3
# is absent, and a step that passed because a toolchain was missing would be a green that
# means nothing -- the same defect class as a check count that folds skipped checks into
# passes. The number it publishes is the README's, reproducible locally by anyone with the
# toolchain: `tools/conformance.sh`.
#
# TWO ARCHITECTURES, ONE BASELINE: the same job on x86_64 and on aarch64 (GitHub's arm64
# runner, free for public repositories; the fielded edge box is aarch64). Both are held to the
# same conformance/baseline-<revision>.yml, and the suite exits 1 on an unexpected failure and
# on a stale entry, so two green jobs mean the same scenarios fail, for the same reasons, on
# both: the architectures' results are equal by construction, not by a reader comparing them.

name: conformance

on:
  push:
    branches: ["**"]
  pull_request:

permissions:
  contents: read

jobs:
  conformance:
    name: Conformance - the two rows, ${{ matrix.os }}
    runs-on: ${{ matrix.os }}
    strategy:
      fail-fast: false
      matrix:
        os: [ubuntu-24.04, ubuntu-24.04-arm]
    steps:
      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
      - uses: erlef/setup-beam@54075bcc5e249e4758d363f27d099f55d843f124 # v1.24.1
        with:
          otp-version: "28"
          elixir-version: "1.18"
      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
        with:
          node-version: "22"
      - run: mix deps.get
      - run: mix compile
      - name: the suite, both revisions, against the baselines
        run: |
          set -uo pipefail
          node --version
          python3 --version
          OUT="$RUNNER_TEMP/conformance" ./tools/conformance.sh
      # REUSE, by the specification's own tool -- CI-ONLY like the conformance number: the
      # gate's REUSE step reads headers; this reads the whole tree by the specification's rules
      # and is the compliance claim CONTRIBUTING makes. The runner's
      # pipx installs it; the version is pinned so the verdict is a function of the tree.
      - name: REUSE - the specification's lint over the whole tree
        if: always()
        run: pipx run reuse==6.2.0 lint

      - name: the suite's results, kept with the run
        if: always()
        uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
        with:
          name: conformance-results-${{ runner.arch }}
          path: ${{ runner.temp }}/conformance
          if-no-files-found: error