duplicate release pipelines on v* tags plus stale CLAUDE.md #37

Open
opened 2026-10-15 11:11:29 +08:00 by Breadway · 0 comments
Owner

Found: full codebase audit 2026-10-15, by reading CI workflows and CLAUDE.md.
Confidence: high.
Location: .forgejo/workflows/release.yml, .github/workflows/release.yml, CLAUDE.md:12-15.

Both Forgejo and GitHub release workflows trigger on v* tags and both write /srv/breadway-dl plus gh release upload, so one tag push races. Separately, CLAUDE.md still documents the old dev/beta-branch model, contradicting AGENTS.md and CONTRIBUTING.md single-trunk docs.

Suggested fix: keep one authoritative release path (or scope triggers so they cannot both fire) and update or remove CLAUDE.md.

Found: full codebase audit 2026-10-15, by reading CI workflows and CLAUDE.md. Confidence: high. Location: .forgejo/workflows/release.yml, .github/workflows/release.yml, CLAUDE.md:12-15. Both Forgejo and GitHub release workflows trigger on v* tags and both write /srv/breadway-dl plus gh release upload, so one tag push races. Separately, CLAUDE.md still documents the old dev/beta-branch model, contradicting AGENTS.md and CONTRIBUTING.md single-trunk docs. Suggested fix: keep one authoritative release path (or scope triggers so they cannot both fire) and update or remove CLAUDE.md.
Sign in to join this conversation.
No labels
bug
ci
enhancement
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Breadway/breadcrumbs#37
No description provided.