Skip to content

feat(tls): install [vault] on CI, then assert the Vault hops' suites (BACKLOG #1317) #405

feat(tls): install [vault] on CI, then assert the Vault hops' suites (BACKLOG #1317)

feat(tls): install [vault] on CI, then assert the Vault hops' suites (BACKLOG #1317) #405

Triggered via pull request September 4, 2026 23:27
Status Failure
Total duration 1h 47m 2s
Artifacts

required-workflow-state.yml

on: pull_request
required contexts belong to active workflows
19s
required contexts belong to active workflows
the required-contexts file matches the server
18s
the required-contexts file matches the server
Fit to window
Zoom out
Zoom in

Annotations

3 errors
the required-contexts file matches the server
Process completed with exit code 1.
the required-contexts file matches the server
Reconcile them in ONE change. If the SERVER is right, edit .github/required-contexts.txt (and the count pinned in tests/test_required_contexts.py, and a negative control per new context -- tests/_negative_controls.py requires one, and reads the list from this same file). If the FILE is right, the fix is on the server and adding to protection is all-or-nothing: the REST endpoint 422s with `already_exists` if any context in the request is already required, and then adds NONE of them, so send only the missing ones.
the required-contexts file matches the server
NAMED IN THE FILE, NOT REQUIRED ON THE SERVER -- the file claims these gate a merge and nothing does: