Skip to content

Slim CI and the guard checks - #76

Merged
a9lim merged 2 commits into
mainfrom
slim/release-protocols
Nov 3, 2026
Merged

a9lim merged 2 commits into
mainfrom
slim/release-protocols

Conversation

@a9lim

@a9lim a9lim commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

CI ran the CPU suite three times (Python 3.11, 3.12, 3.13) without xdist and with coverage: 12-19 minutes a push for a suite that takes 47 s locally with -n 8. It now runs once, on 3.13, with -n auto and no coverage. The job names branch protection requires (lint, typecheck, test) stay.

Gone, as checks a careful change does not need:

  • the build job and scripts/check_package_isolation.py (a stale build/lib guard; release.yml builds the wheel);
  • the generated-types --check step in typecheck (tests/invariants/test_webui_types_parity.py checks the same in pytest);
  • the Ledger ratchet (check-ledger.mjs, ledger-ratchet.json) and the test-wiring meta-check (check-test-coverage.mjs);
  • tests/invariants/test_layering.py and test_boundary_guard.py. The layer order stays documented in AGENTS.md and the package AGENTS.md files.

Local: ruff clean, pytest -q -m "not gpu" -n 8 5971 passed in 42 s, npm run check 31 s.

a9lim added 2 commits November 2, 2026 19:00
…t and no coverage; the package-isolation build, the Ledger ratchet, the test-wiring meta-check and the layering and server-boundary tests go (the layer order stays documented)
@a9lim
a9lim merged commit 09fc3f3 into main Nov 3, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant