Ok - there is now a release branch for 1.0.0 : rel-1.0.0 Moving forward the release process will be: • Fixes are merged to

main

via PR as normal • Approved fixes from Product Management (Those tagged with canvas-mvp should be cherry picked over to the release branch) • When QA is happy, release branch can be tagged with either

v1.0.0-rc1

for a release candidate or

v1.0.0

for a full release. We will be creating multiple release candidate tags daily

Is there a way to add a requirement in the release CI that the e2e tests pass first for the commit tagged

I am looking into that

Also relatedly adding the same e2e coverage for the docker entrypoint in addition to npm: https://github.com/OpenHands/agent-canvas/pull/992 Caught some bugs via this, so seems promising