ci: add CI workflow and refresh the dependency lock

Merged
WI
21d ago
+1610-2886

Summary

This repo had no CI — no .github directory, nothing running on a pull request. This adds a workflow gating lint, type check and tests across the supported 3.10–3.13 matrix, and refreshes a lockfile that had gone stale.

Lockfile drift

uv.lock was pinned to stackone-ai 2.8.0 (2.10.1 released) and google-adk 1.31.1 (2.9.0 released). Both are refreshed here.

Nothing broke on the newer versions — all 32 tests pass on the upgraded stack, including across a major google-adk bump. The drift was stale pinning, not an incompatibility. The workflow uses uv sync --locked, so a dependency change that was not re-locked can no longer merge silently.

Two fixes needed to make CI green on arrival

Adding gates that fail immediately would be pointless, so:

Three pre-existing ruff violations — a 113-char line in plugin.py, an unsorted import block, and an unused google.genai.types import in tests/test_tools.py.

mypy's hardcoded python_version = "3.10". This one is worth reading. It forced mypy to parse dependency stubs with 3.10 grammar while the environment can legitimately contain 3.12-only packages. numpy ≥2.5 (requires-python >=3.12, reached transitively via stackone-ai) uses type statements, so mypy died on a syntax error inside numpy's own .pyi:

numpy/__init__.pyi:737: error: Type statement is only supported in Python 3.12 and greater  [syntax]

The pin was incoherent — it asserted "check as 3.10" while the installed tree could be 3.12-only. Unsetting it targets the running interpreter, so each matrix job checks against its own version. That is also broader coverage than the pin gave. Verified end to end:

Pythonnumpy resolvedruffmypypytest
3.102.2.6passpass32 passed
3.112.2.6passpass32 passed
3.122.5.3passpass32 passed
3.132.5.3passpass32 passed

Integration smoke test — documented, not wired

The suite here replaces StackOneToolSet with a MagicMock; the real SDK is imported exactly once, for an exception class. It therefore passes regardless of SDK behaviour and cannot catch an SDK regression.

sdk-conformance carries a smoke script that drives the real SDK through the real plugin against a mock StackOne API. I ran it against this branch's refreshed dependencies — it passes, including that the plugin's declaration carries a raw JSON Schema rather than a lossy rebuild.

It is not wired into CI: sdk-conformance is a private repository and this repo has no secret configured to clone it (gh secret list is empty, and I do not have admin here to add one). Wiring it needs a deploy key or PAT added first. Until then the README documents how to run it locally.

Deliberately not done

ruff format is not gated — two files carry pre-existing formatting drift, and reformatting them is unrelated to adding CI. Worth a separate pass if you want formatting enforced.

🤖 Generated with Claude Code


Summary by cubic

Adds CI to this repo (previously none) and refreshes a stale uv.lock. The workflow gates ruff, mypy, and pytest on Python 3.10–3.13 with uv sync --locked, so a dependency change that isn't re-locked can no longer merge.

Dependencies

  • uv.lock was refreshed to stackone-ai 2.10.1 and google-adk 2.9.0; after merging main it also carries stackone-ai's <3.0.0 cap and the 0.2.1 version from #27 (regenerated, not hand-merged).
  • pyjwt 2.15.1, urllib3 2.8.0, authlib 1.9.1, certifi 2026.10.23, and truststore 0.10.5 are pinned to clear their remaining open alerts; all 32 tests still pass.

Notes

  • Removes mypy's hardcoded python_version = "3.10" and fixes three pre-existing ruff violations so the gates are green on arrival.
  • The integration smoke test is documented in the README but not wired into CI; this repo has no credential to clone sdk-conformance.
  • The job is capped at 15 minutes and checkout discards the token for later steps; ruff format is not gated because two files carry pre-existing formatting drift.