About release - 🔧 PR for review: Fix stale Docker image tags + add version consistency CI + skill for ship-release/bump-commit https://github.com/OpenHands/OpenHands/pull/13315 While investigating our release process (for my own development PR), I found that Docker image tags in 4 files have been stuck at

1.2

since the 1.2.0 release — the 1.3.0 and 1.4.0 releases only bumped the 3 core version files (

pyproject.toml

,

package.json

,

package-lock.json

) but missed updating the image references in

Development.md

,

containers/dev/compose.yml

,

docker-compose.yml

, and the Kubernetes README. This PR: 1. Fixes the stale tags — updates all 4 files to match the current

1.4.0

/ SDK

1.12.0

versions 2. Adds a

check-version-consistency.yml

CI workflow — runs on every PR to validate that version numbers and Docker image tags are consistent across all 7 files, so this can't silently drift again 3. Adds a

ship-release

skill — documents the full release checklist (which files to change, in what order) and how to pin SDK packages to unreleased git commits for testing Would appreciate a review when you get a chance 🙏

Just a comment. But overall looks good. I think with the version consistency job the agent server image will get updated as part of when we update sdk in the repo. Not as part of a release which makes more sense

Thanks! Asking agent to rename the skill for consistency 🙂 Maybe calling the skill

update-sdk

would be more appropriate