Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
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 1 file
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
|
s2d2 fix pass (requested by guillaume@stackone.com in Slack): no code change. Checked the cubic compare-link thread: tag v0.2.0 exists, so the link is valid. Replied and resolved. Note for merge: no v0.2.1 tag exists yet and main is already at 0.3.0 (tag v0.3.0), so this entry is a backfill. |
Adds the 0.2.1 entry to
CHANGELOG.md.pyproject.tomlandstackone_adk/__init__.pyare already at 0.2.1 on main.0.2.1 needs to reach PyPI before stackone-ai 3.0.0 does (stackone-ai-python#200). The published 0.2.0 depends on
stackone-ai[mcp]>=2.8.0with no upper bound, andstackone_adk/__init__.pyimportsSearchConfigandSearchMode, which 3.0 removes. Once 3.0 is out, a freshpip install stackone-adk==0.2.0on Python 3.11+ resolves stackone-ai 3.0 and fails on import.After merge:
rm -rf dist/ && uv build && uv publish, then tagv0.2.1, following the existingv0.2.0tag.🤖 Generated with Claude Code
Summary by cubic
Adds the 0.2.1 entry to
CHANGELOG.md, covering thestackone-ai[mcp]cap and the plugin description update. This lets 0.2.1 ship to PyPI beforestackone-ai3.0 removesSearchConfigandSearchMode, which would otherwise break fresh installs of 0.2.0.Written for commit 78f2cbf. Summary will update on new commits.