Repository navigation
feat!: move to StackOne AI SDK 3.0 and its search and execute tools (ENG-3175) - #30
Conversation
There was no CI in this repo — nothing ran on a pull request. Adds a workflow gating lint, type check and tests across the supported 3.10-3.13 matrix. `uv sync --locked` is used so a dependency change that was not re-locked cannot merge. That immediately mattered: uv.lock had drifted to stackone-ai 2.8.0 while 2.10.1 was released, and google-adk 1.31.1 while 2.9.0 was released. Both are refreshed here and the suite passes on the new versions, so the drift was stale pinning rather than an incompatibility. Two fixes were needed to make the gates green rather than red on arrival: - Three pre-existing ruff violations (a 113-char line, an unsorted import block, an unused `google.genai.types` import). - mypy's hardcoded `python_version = "3.10"`. It made mypy parse dependency stubs with 3.10 grammar while the environment can hold 3.12-only packages — numpy >=2.5 (requires-python >=3.12, reached transitively via stackone-ai) uses `type` statements, which failed as a syntax error. Unsetting it targets the running interpreter instead, so each matrix job checks against its own version. Verified on 3.10 (numpy 2.2.6) through 3.13 (numpy 2.5.3). `ruff format` is deliberately not gated: two files carry pre-existing formatting drift, and reformatting them is unrelated to adding CI.
Keeps main's stackone-ai <3.0.0 cap and 0.2.1 version from #27. uv.lock is regenerated rather than hand-merged, with pyjwt 2.15.1 and urllib3 2.8.0 to clear their remaining open alerts. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…' into will/eng-3175-sdk-3
stackone-ai 3.0 lists and runs every tool over StackOne's MCP endpoint and searches
on the server, so the plugin no longer discovers accounts, calls the SDK's private
_build_tools(), or configures a search backend. One toolset serves both modes:
mode="search_and_execute" asks for the search_execute tool mode, whose
stackone_search_actions / stackone_execute_action / stackone_list_accounts span
every account in scope.
Tools declare the served schema and required list (to_openai_function) and return
the server's {isError, result} object. Requires Python 3.11.
uv.lock is re-locked once stackone-ai 3.0.0 is on PyPI.
… at most 50 (ENG-3175)
…lones the smoke test's siblings
…' into will/eng-3175-sdk-3
Generated by a one-off CI job on this branch (run 40878959593) because the local index proxy does not serve 3.0.0 yet; that job is removed here. Drops the 2.x-only and Python 3.10 dependencies.
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.
There was a problem hiding this comment.
All reported issues were addressed across 11 files
Heads up: you’re close to your included review allowance. Set a flex budget so reviews don’t pause.
View guided diff | Turn on auto-fix | Re-trigger cubic
There was a problem hiding this comment.
0 issues found across 1 file (changes from recent commits).
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Heads up: you’re close to your included review allowance. Set a flex budget so reviews don’t pause.
Requires human review: Major breaking upgrade to StackOne AI SDK 3.0: it removes public plugin options/exports, renames the search/execute tools, and changes result shapes; the new SDK-owned account discovery and tool exposure need human sign-off.
Tip: Get a Slack DM when cubic finishes reviewing your PRs. Connect Slack
View guided diff | Turn on auto-fix | Re-trigger cubic
Part of ENG-3175. Moves the plugin to StackOne AI SDK 3.0.
uv.lockpinsstackone-ai3.0.0 from PyPI (published 2026-10-29); CI passes on 3.11–3.13.This branch includes #26 (the CI workflow and lock refresh, approved) as a merge commit, so its diff shows here too. Merge #26 first and this diff shrinks to the plugin change.
stackone-ai>=3.0.0,<4.0.0(the[mcp]extra no longer exists); Python 3.11+, as the SDK requires; the CI matrix is 3.11–3.13. Version 0.3.0.GET /accountsdiscovery and its call to the private_build_tools()are gone; the SDK discovers accounts itself. If tools can't be loaded, the plugin still logs a warning and registers none.mode="search_and_execute"maps to the SDK'stool_mode="search_execute": StackOne'sstackone_search_actions,stackone_execute_actionandstackone_list_accounts, served by the server.search=,SearchConfigandSearchModeare removed.requiredlist (to_openai_function()) and return the server's{isError, result}as written.Checks: 20 tests pass; ruff and mypy clean. sdk-conformance's
smoke_adk.pyand the plugin's search mode pass through the real SDK branch (StackOneHQ/stackone-ai-python#231) against the mock API.Live (production API, Gemini 3.1 Pro, a Google Calendar account): ADK agents passed in individual and search mode. Production still serves the per-account pair, so search mode there exercised that; the trio needs unified-cloud-api#9417 (merged).
Update: on the merged server (#9417) the plugin needs no code change: the SDK presents one account's own pair as
stackone_search_actions/stackone_execute_action, so the plugin registers those names however many accounts are in scope (stackone_list_accountsonly with several, at most 50). README, CHANGELOG and docstrings updated to say so.