ci: isolate the stable release index checkout #55
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/eco28-release-index-isolation"
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?
Last remaining copy of the shared CI checkout path tracked by ECO-28 and ECO-56 (breadboard).
The stable release index step deleted and reused the fixed
/tmp/bread-ecosystem-cipath. Two concurrent stable releases on the shared self-hosted runner, or any older workflow still running a broad/tmp/bread-ecosystem-ci-*cleanup, could remove or overwrite the checkout mid-run. The beta step inrc-release.ymlwas already fixed this way in #51; this mirrors it for the stable path.The clone now goes to a unique
mktempdirectory outside the legacy prefix, and an EXIT trap removes only that directory, including when the clone or index generation fails.Verified:
bash -n.regenerate index.jsonstep, run with the clone stubbed to a local tree, cleans up only the invocation's directory on both success and failure, while a sibling checkout under the legacy/tmp/bread-ecosystem-ci-*prefix stays intact.