molecule-ai/molecule-sdk-python
41
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix(sdk-python): correct REQUIRED_CONTEXTS context names in merge queue workflow #21

Closed
sdk-dev wants to merge 3 commits from fix/merge-queue-contexts-sdk into main
pull from: fix/merge-queue-contexts-sdk
merge into: molecule-ai:main
Conversation 1 Commits 3 Files Changed 7
+430 -9

3 Commits

Author SHA1 Message Date
sdk-dev a4cf7bc75c fix(sdk-python): correct REQUIRED_CONTEXTS context names in merge queue workflow
[Do] Admin ack
Details
sop-checklist / all-items-acked SOP checklist acknowledged
Details
Test / test (3.11) (pull_request) Successful in 1m59s
Details
Test / test (3.12) (pull_request) Successful in 1m46s
Details
Test / test (3.13) (pull_request) Successful in 1m31s
Details 
The workflow override set REQUIRED_CONTEXTS=CI / test (pull_request),
but Gitea's status API reports contexts as "Test / test (3.13) (push)"
for cron-triggered/scheduled runs. This mismatch caused the queue script
to always see the context as "missing" and never attempt a merge.

Fix: update REQUIRED_CONTEXTS to the live API-reported context names
(all Python 3.x matrix entries) and restore the SOP checklist gate
context (dropped when the workflow overrode the script defaults).

Verified against:
https://git.moleculesai.app/api/v1/repos/Molecule-AI/molecule-sdk-python/statuses/main

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
 2026-05-16 19:22:23 +00:00
sdk-dev 56e963bb87 fix(docs): update stale docstring to reflect shipped inbound delivery paths
[Do] Manual ack
Details
Test / test (3.12) (pull_request) Successful in 2m1s
Details
Test / test (3.11) (pull_request) Successful in 2m8s
Details
Test / test (3.13) (pull_request) Successful in 2m16s
Details
sop-checklist / all-items-acked All items acknowledged
Details
sop-checklist / [Do] Done
Details 
The module docstring claimed "No inbound A2A server is bundled here yet"
but A2AServer (push) and PollDelivery (poll) have been implemented and
documented since Phase 30.8b/30.8c. Replaced the outdated claim with a
concise description of both delivery modes and how run_agent_loop uses them.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
 2026-05-15 20:19:09 +00:00
sdk-dev 6a1b2bf1a1 fix(docs): remove stale sdk/python/ path references
Test / test (3.11) (pull_request) Successful in 2m7s
Details
Test / test (3.12) (pull_request) Successful in 2m19s
Details
Test / test (3.13) (pull_request) Successful in 2m28s
Details
sop-checklist / all-items-acked test
Details
[Do] Manual ack
Details 
The repo was restructured from sdk/python/ to top-level molecule_agent/
and molecule_plugin/. Four doc references still pointed to sdk/python/:

- molecule_agent/__init__.py: sdk/python/examples/remote-agent/ → examples/remote-agent/
- molecule_agent/README.md: sdk/python/examples/remote-agent/ → examples/remote-agent/
- molecule_plugin/__init__.py: sdk/python/README.md → repo root README.md
- examples/remote-agent/README.md: sdk/python/examples/remote-agent/run.py → examples/remote-agent/run.py

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
 2026-05-15 10:18:29 +00:00