ci: remove shared temp cleanup from tag release workflows #17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/pad-16-isolated-tag-index"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tag release index regeneration now clones into an invocation-specific mktemp directory and removes only that directory on exit, including failed clones or index generation. Concurrent jobs keep their own checkouts intact.
Verified YAML parsing, embedded Bash syntax, diff checks, and four concurrent mocked workflow steps with distinct clone paths. Success and failure cleanup passed while a sibling active directory survived. No release or deployment was run.
Closes #16
Not merged in this review pass. The mktemp + trap changes are right, but the prefixes kept in this branch (
/tmp/bread-ecosystem-ci-rc-XXXXXX,/tmp/bread-ecosystem-ci-release-XXXXXX) still match an older workflow'srm -rf /tmp/bread-ecosystem-ci-*, so a concurrent legacy job can still delete this checkout during the rollout window. ECO-56 asks for a prefix older workflows cannot match; the breadclip/breadmon/breadshot siblings use/tmp/bread-index-XXXXXX. Switch both workflows to such a prefix and this can merge.Merged. The branch was already current on main (
08aff4a) and mergeable.Verified independently:
bash -n(rc-release.yml 4 blocks, release.yml 5 blocks).rm -rf /tmp/bread-ecosystem-ci-*and the fixed/tmp/bread-ecosystem-cipath are gone, replaced by per-runmktempdirectories with anEXITtrap.