Repository navigation
v0.5.3 — CI and entrypoint coverage
Housekeeping release: no change under src/; adds CI and tests only.
Added
- CI actually runs the tests. New
.github/workflows/test.yml(pytest +
ruff checkon Python 3.10/3.11/3.12, on every push and PR tomain). Until
now the only workflow waspublish.yml, which builds and uploads on av*
tag without ever invoking pytest or ruff — which is how 0.5.1 went out green
while onemcprelease away from never starting.ruff format --checkis
intentionally not in the workflow: it flags 5 files of pre-existing drift
from a newer ruff, and a gate that is red on day one gets disabled on day two. - Entry-point smoke tests (
tests/test_entrypoint.py, 8 tests). Covers the
path a real MCP client walks and no other test touched:console_scripts
metadata →gitlab_ci_mcp.server:main→mcp.run()→ stdio → clean exit on
EOF, plus protocol-levellist_tools()/list_resources()and a check that
the server builds with no credentials in the environment. Offline; no GitLab,
no token. Verified mutationally: makingmain()fail at runtime leaves the
previous 21 tests andruff checkgreen and turns only these red.
Changed
[tool.pytest.ini_options]inpyproject.tomlanchors pytest's rootdir at
the repo, so a straypytest.iniin a parent directory can no longer inject
itsaddoptsand break collection before a test runs.