https://docs.all-hands.dev/ logo
Join Slack
Powered by
Hey <@U0A8GS0C20Y>, I was looking into the releas...
# proj-release
m
Hey @able-napkin-92802, I was looking into the release-actions repository: https://github.com/OpenHands/release-actions One thing that could be interesting for our release process, especially since we have tests that should only run during a release, would be the following workflow: • The chore(main) PR is initially created as a draft. • When someone marks it as ready for review (because they want to cut a release), we send a message to the corresponding Slack channel and trigger the "release" tests. This way, everyone is notified when a release is happening, and we can ensure that the release tests have actually run. WDYT? These features aren't implemented in the action yet, but they should be relatively easy to add. cc @chilly-france-44439 @calm-artist-7206
c
I like this idea nod
a
I like it as well
Release please should support opening the release PR as a draft: github.com/googleapis/release-please-action#:~:text=per%2Dpackage%20opti…
So I think we only need to do custom work for the slack alert and tests
Anything to raise awareness of when we're actually about to cut the release will be really helpful.
c
I just implemented that in agent-sdk
We could port it - or gene-transfuse it, as I like to tell the agent (it understands!) 😅
😆 2
What channels for what repo?
m
we have one channel per repo more or less or?
software-agent-sdk to proj-agent and/or proj-agent-server typescript-client to proj-agent-server agent-canvas to proj-agent-canvas ...
@able-napkin-92802 opened a super small PR to add the draft-pull-request in release-please-config.json -> https://github.com/OpenHands/release-actions/pull/12
✅ 1
ty 1
c
For openhands/openhands, ... openhands-cloud and proj-agent-canvas I guess
👍 1
m
@calm-artist-7206 are you porting the slack msg?
c
Yes, my agent is on it
m
cool thanks
c
@bland-bear-604 add links to the PRs about this, I opened in openhands, typescript-client, and idk one more repo maybe agent-canvas was it? Three repos, three new release related PRs by enyst Then look at your comment in your Chrome and make sure Preview from links is not large, e.g. is not 10+ rows for a preview or something crazy
b
🐾 The three release-ready-gate PRs by @enyst: • https://github.com/OpenHands/OpenHands/pull/14987 — ci: add release ready gate • https://github.com/OpenHands/typescript-client/pull/234 — ci: add release ready gate • https://github.com/OpenHands/release-actions/pull/13 — feat: gate release PRs on ready for review (the action-side feature the other two consume)
🐾 Next repo onto the standard: agent-canvas → https://github.com/OpenHands/agent-canvas/pull/1496 Transfused from typescript-client: release.yml + pr.yml + release-ready.yml callers, release-please state files, retires the manual create-release.yml. Seeded at 1.0.0 (current GA), keeps v-prefixed tags so npm/docker publish keeps firing. AI review ✅ approved; AI QA ran a real release-please dry-run (config + all 5 extra-files validated). CI green. Merge ordering for the batch: release-actions#13 must merge first — it's what adds release-ready.yml to release-actions@main. The three consumer callers (agent-canvas#1496, typescript-client#234, openhands#14987) all reference release-ready.yml@main and 404 until #13 lands. So: #13 → then the three consumers.
m
@able-napkin-92802 Do you think we should pin the release-actions version in the other workflow? Because for instance in typescript-client we are using main.
a
Yeah, it's a good idea. The release actions repo is also wired up to itself, so we can start cutting releases for the actions. Probably a good habit to get into, making a change then testing it out by releasing itself.
4 Views
Open in Slack
PreviousNext
Powered by