Repository navigation
feat(blue): activate the bs-autobot optional extra (PyPI 0.1.1 live) - #1124
PurpleCHOIms wants to merge 3 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bc443ec385
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| blue = ["bs-autobot>=0.1.1"] | ||
| all = ["decepticon[neo4j,telemetry,mcp,blue]"] |
There was a problem hiding this comment.
Update uv.lock when adding the Blue extra
The committed uv.lock still lists only neo4j, telemetry, mcp, and all in Decepticon's provides-extras, contains no bs-autobot dependency, and retains the previous all definition. Both Python jobs in .github/workflows/ci.yml run uv sync --dev --locked (lines 214 and 320), so this metadata change requires a lockfile update even when Blue is not selected. The installed CLI describes --locked as “Assert that the uv.lock will remain unchanged”; these jobs therefore cannot accept the required re-resolution. Regenerate and commit the workspace lockfile with the extra.
Useful? React with 👍 / 👎.
| blue = ["bs-autobot>=0.1.1"] | ||
| all = ["decepticon[neo4j,telemetry,mcp,blue]"] |
There was a problem hiding this comment.
Record the new installation behavior in the root changelog
This commit adds the user-visible decepticon[blue] installation option and changes decepticon[all] to install AutoBot, but leaves the root CHAGELOG.md unchanged. Add an Unreleased entry describing the new extra and the additional dependency for existing all consumers, with the associated PR link when available. The repository explicitly requires this change tracking before opening or updating a PR.
AGENTS.md reference: AGENTS.md:L3-L7
Useful? React with 👍 / 👎.
|
Superseded by #1127 (re-based onto current main with the lazy KG import fix). |
AutoBot 0.1.1 is now published at PyPI, so the deferred optional extra can be activated safely:
decepticon[blue]installsbs-autobot>=0.1.1.autobotgraph through thedecepticon.agentsentry-point; theautobotsubagent throughdecepticon.subagents.bs-autobot==0.1.1, merged manifest 28 graphs withautobot: autobot.agent.autobot:graph, mcp v1 retained; full non-slow Decepticon suite 5794 passed.This is the final activation piece of migration stage 2c. The langgraph container boot hook from PR #1117 auto-installs bs-autobot when
DECEPTICON_ENABLE_BLUE=1; this extra covers native Python co-install.