ci: isolate stable release ecosystem clone #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
The stable release workflow still runs
rm -rf /tmp/bread-ecosystem-ciand clones Breadway/bread-ecosystem into that fixed path before generating index.json. Concurrent stable releases on the shared runner can remove or overwrite another job's active clone. The dev and RC workflows already use per-run mktemp directories. Update only .forgejo/workflows/release.yml to use a unique temporary directory and clean up that directory, then verify the workflow change.PR #10 replaces the shared
/tmp/bread-ecosystem-cipath with a unique mktemp directory, uses it for the ecosystem clone/index script, and removes it after index generation. Verified workflow YAML, embedded shell syntax (bash -n), andgit diff --check. #10Fresh CI
check / check (push)passed on PR #10 commit58f3e00(57s). The card remains in REVIEW for independent review.Reviewed PR #10, ready to merge. Acceptance criteria: (1) the stable release uses an isolated per-run ecosystem checkout, implemented by
mktempand cloning into that path at.forgejo/workflows/release.yml:53-56; (2) index generation uses that checkout and removes it afterward, at lines 57-58. The diff stays within the requested workflow file. No behavioral test was added; the implementer reports YAML parsing, embeddedbash -n, andgit diff --check, and CI is green on58f3e00. PR #10 is mergeable. Note: cleanup only runs after successful clone and index generation; a failure can leave its unique directory on the self-hosted runner, but this does not undermine the requested concurrency isolation.