Skip to content

Confirmed from the registry: both releases were there all along #50

Confirmed from the registry: both releases were there all along

Confirmed from the registry: both releases were there all along #50

Workflow file for this run

# Validates this repository's directory fragment.
#
# The estate-wide merge catches contested authority and dangling references
# across repositories, but it runs elsewhere and cannot say which repository
# caused them. This runs here, so a bad fragment fails at the point it is made.
name: Directory
on:
push:
branches: ['**']
pull_request:
jobs:
fragment:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '22'
# The emitter reads the charter, so a fragment that disagrees with the
# charter is a fragment that was edited by hand.
- name: Emit
run: node scripts/directory.mjs
# The estate authors the AAO standard. Every charter in it was
# non-conformant until this ran.
- name: Charter conforms
run: node scripts/check-charter.mjs
- name: Check
run: node scripts/check-directory.mjs --external person/michael
# A committed fragment that differs from a freshly emitted one means
# someone edited the JSON instead of the source it comes from.
- name: Committed fragment matches the emitter
run: git diff --exit-code -- directory.fragment.json
# The fragment must be SERVED, not merely committed. It lived only at the
# repository root, where a Next.js app never serves it — so the estate's
# federated directory could not be assembled by anyone without a git
# checkout, which defeats the entire point of federating it.
- name: The fragment is served, and matches the source
run: |
test -f public/directory.fragment.json || { echo "the fragment is not in the served directory"; exit 1; }
diff -q directory.fragment.json public/directory.fragment.json