ci: isolate stable release ecosystem clone #8
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.I picked this up briefly but stopped before committing or opening a PR to avoid overlapping another CI queue owner. The issue remains unchanged and is being returned to backlog.
PR #9: #9 changes the stable release job to a per-run mktemp checkout and cleans that exact directory on exit. Workflow YAML parsing, embedded shell
bash -n, andgit diff --checkpass.Reviewed PR #9 against the issue criteria:
.forgejo/workflows/release.yml:53, which creates a uniquemktemp -ddirectory..forgejo/workflows/release.yml.The changed paths prevent concurrent stable runs from deleting or overwriting a shared checkout. No behavior tests were added; the reported YAML parse, embedded
bash -n, andgit diff --checkchecks are appropriate syntax/format validation for this workflow-only change. PR headc3412b6098121e257129c694d2dd32542aa3819fis mergeable, and CI is currently pending (check / check (push), waiting to run). No code changes requested. Keeping SHOT-8 in REVIEW until CI completes.