https://docs.all-hands.dev/ logo
Join Slack
Powered by
1.22.1 was out last night (cc <@U093U7MJ44B>) <htt...
# proj-agent
c
1.22.1 was out last night (cc @millions-afternoon-47582) https://github.com/OpenHands/software-agent-sdk/releases/tag/v1.22.1
ā¤ļø 1
thankyou 1
l
Yeah, I realeased this because it was needed to fix the llm switch tool, thanks for starting it!
šŸ™Œ 2
m
Hello @quick-window-91705, when you have a moment, could you please update and release the automations using the new SDK version? At the moment, Iā€™m unable to update the SDK version in agent-canvas without this update. Thank you very much! thankyou
Copy code
SDK Version Sync Check
ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€

Expected SDK version: 1.22.1 (from dev-safe.mjs)
Automation package: openhands-automation==1.0.0a2 (from dev-with-automation.mjs)

Fetching <https://pypi.org/pypi/openhands-automation/1.0.0a2/json>
Checking openhands-automation==1.0.0a2 SDK dependencies:

  openhands-sdk             āœ— 1.22.0 (expected 1.22.1)
  openhands-tools           - not a direct dependency
  openhands-workspace       āœ— 1.22.0 (expected 1.22.1)
  openhands-agent-server    - not a direct dependency

Version mismatch detected!

The released openhands-automation==1.0.0a2 uses different SDK versions than expected.

Mismatched packages:
  - openhands-sdk: 1.22.0 (expected 1.22.1)
  - openhands-workspace: 1.22.0 (expected 1.22.1)

To fix, update one of the following:
  1. Update DEFAULT_AGENT_SERVER_VERSION in scripts/dev-safe.mjs to match the automation release
  2. Release a new version of openhands-automation with SDK dependencies pinned to 1.22.1
  3. Update DEFAULT_AUTOMATION_VERSION in scripts/dev-with-automation.mjs to a newer release
šŸ‘ 1
@quick-window-91705, would it be possible to release automation with the new SDK version today? At the moment, agent-canvas is blocked by this issue. Once the SDK version is updated in agent-canvas, I will be able to merge the public skills pull request, making the public skills available in agent-canvas. Thank you so much for your help! thankyou
acknowledged 1
q
@nutritious-balloon-65098 please update the SDK versions and bump the pyproject value, then open a PR on the openhands/automation repo
n
I'm on it! Rohit Malhotra can track my progress here.
Summary of Changes What was requested Update the SDK versions in the automation repo and bump the package version, then open a PR on 
OpenHands/automation
. Checklist ā€¢ āœ… Updated 
openhands-sdk
 from 
1.22.0
ā†’ 
1.22.1
in 
pyproject.toml
ā€¢ āœ… Updated 
openhands-workspace
 from 
1.22.0
ā†’ 
1.22.1
in 
pyproject.toml
ā€¢ āœ… Bumped package version from 
1.0.0a2
ā†’ 
1.0.0a3
in 
pyproject.toml
ā€¢ āœ… Regenerated 
uv.lock
 via 
uv lock
to reflect the updated pins ā€¢ āœ… Opened PR #117 on 
OpenHands/automation
targeting 
main
Conciseness Only the two files that needed changing were touched ā€” 
pyproject.toml
(3 lines) and 
uv.lock
(regenerated). No extraneous changes were made.
q
@nutritious-balloon-65098 can you tag and cut a release for the latest commit of the PR also if agent.md doesn't have instructions regarding this release procedure please add it to the same pr, push the commit, then tag the latest commit on the pr
n
I'm on it! Rohit Malhotra can continue tracking my progress here.
Summary of work Request 1 ā€” Update SDK versions, bump pyproject version, open a PR āœ… ā€¢ 
openhands-sdk
pinned version updated 
1.22.0
ā†’ 
1.22.1
in 
pyproject.toml
 ā€¢ 
openhands-workspace
pinned version updated 
1.22.0
ā†’ 
1.22.1
in 
pyproject.toml
 ā€¢ Package version bumped 
1.0.0a2
ā†’ 
1.0.0a3
in 
pyproject.toml
 ā€¢ 
uv.lock
regenerated to reflect all three changes ā€¢ PR opened: OpenHands/automation #117 (
bump/sdk-1.22.1
ā†’ 
main
) Request 2 ā€” Tag & cut a release; add release procedure to AGENTS.md if missing āœ… ā€¢ Checked AGENTS.md ā€” no release procedure section existed ā€¢ Added a Release Procedure section to 
AGENTS.md
covering: ā—¦ Automated path (Prepare Release GitHub Actions workflow) ā—¦ Manual path (edit ā†’ 
uv lock
ā†’ commit ā†’ tag ā†’ push) ā—¦ Table of what each tag push triggers (
pypi-release.yml
, 
tag-image.yml
) ā—¦ SDK dependency bump checklist (including deploy-repo 
AUTOMATION_SHA
update reminder) ā€¢ AGENTS.md commit pushed to the PR branch (
56e61a0
) ā€¢ Tag 
1.0.0a3
applied to the new HEAD commit (
56e61a0
) and pushed ā€” triggering the PyPI publish and Docker retag workflows No extraneous changes were made.
q
@nutritious-balloon-65098 the docker tag ci failed, please investigate and fix this
n
I'm on it! Rohit Malhotra can continue tracking my progress here.
Here's a summary of all work done since the last summary (the Docker tag CI investigation and fix): Work Summary Request: Investigate and fix the Docker tag CI failure ā€¢ Investigated root cause ā€” confirmed a race condition: 
tag-image.yml
and 
ghcr-build.yml
both trigger on 
push:tags
and run concurrently. The retag workflow tried to inspect 
sha-56e61a0...
at 
19:03:28
but the Docker build didn't finish pushing that image until 
19:04:05
(37 seconds later), causing an immediate hard failure. ā€¢ Immediate fix ā€” re-ran the failed 
tag-image
workflow via the GitHub API; it passed cleanly since the image was available. Tag 
1.0.0a3
is now correctly live on GHCR. ā€¢ Permanent fix ā€” replaced the one-shot 
docker buildx imagetools inspect
check in 
.github/workflows/tag-image.yml
with a 30 Ɨ 10s retry loop (5-minute budget). Future releases will wait for the Docker build to finish pushing rather than racing and failing hard. ā€¢ Change is minimal and targeted ā€” only the 
run:
block of the "Add tags to existing image" step was modified; no other workflow logic was touched. ā€¢ Committed as 
7cdc10f
and pushed to PR #117.
q
@millions-afternoon-47582 cut a new release you can update the agent canvas automation ref now
thankyou 1
3 Views
Open in Slack
PreviousNext
Powered by