I think we could auto-merge the automated PRs that...
# proj-agent
c
I think we could auto-merge the automated PRs that clean up the
.pr/
directory from main. 🤔 It’s a type of PRs that only deletes files, nothing else must happen in its diff WDYT? An Automation, e.g. daily or on PR opened, could do it. Example: https://github.com/OpenHands/OpenHands/pull/19050
q
can we do it before rhe pr merged? or is the concern that ci has to rerun when this happens? and if so can we have the release please pr delete the files?
c
Yes, it's because of CI, sorry but it seemed such a waste because it was running so often...
Oh, yes, the release pr sounds good!
@bland-bear-604 lets look into it, for release-please -using repos make an issue on the release-action repo; for sdk on sdk. investigate and be clear on what to do. then give me here a concise version
🐾 1
b
Yes—fold deletion into the release PR’s normal create/update commit, and retire the separate cleanup PRs 🐾 Filed release-actions #22 for both release-please engines, and SDK #6334 for its current
prepare-release
workflow. Keep the release-tree guard. Canvas live E2E also writes
.pr/
back to PR heads; release PRs need that evidence in Actions artifacts instead, or cleanup loops. Normal release CI stays. AI investigation for Engel.
c
fyi we also want to clean up the existing, then, if this replaces it. use our cc to implement the issues, and our codex to review until they're green and great - then ask all-hands-bot to review. HUMAN: clean up the temporary .pr/ artefacts in the release PR
🐾 1
b
SDK: #6335 is green and passed the second local Codex review. all-hands-bot review is requested. The old cleanup producer is removed in that PR. The shared release driver needs another pass: Codex found base-snapshot and large-deletion commit issues. I’m holding it and the three caller rollouts until the revised plan/dependency setup is confirmed. Nothing merged. AI agent (SmolPaws), on behalf of Engel.
c
So I merged those two on the sdk, is there anything else to do for the next release branch or wip branch if any?
🐾 1
b
Nothing extra for the next SDK release: both merges are on main, and the next Prepare Release run will include cleanup in its normal commit. There is no open rel-* release PR to refresh. 🐾 I did find the old draft #4723 for TypeScript 1.40.0 (last updated Aug 31). Today’s SDK release workflow already prepares and publishes the TypeScript client together with Python. That draft looks superseded; I would close it rather than refresh it. I left it untouched. AI agent (SmolPaws), on behalf of Engel.
Release cleanup update: shared action #23 is up, with 23 local tests passing and clean Codex review. Its test workflow needs maintainer approval for the fork run. All three caller PRs have green CI: Canvas #19109, extensions #869, automation #664. The bot approved extensions and automation; Canvas review is requested. All three stay draft until the shared action lands. Nothing merged by me. AI agent (SmolPaws), on Engel’s behalf.