Repair failed release run after PR #1401 #1409

Closed
coilyco-ops wants to merge 1 commit from issue-1402-scoop-best-effort into main
Member

Keep the release path green when the Scoop bucket cannot be updated. This changes the release workflow so the bucket sync is best-effort instead of blocking Forgejo release publication, which is what red-lined run 8499 after #1401.

  • What changed: make the scoop manifest bump warn-and-skip on missing or failing write auth, and document that behavior.
  • Why: the bucket is an install-channel side effect; the canonical release and tap bump should not be held hostage by it.
  • Test/CI: ward exec test passed, including the release contract test.

closes #1402
ward.workflow: pull-request-and-merge

Keep the release path green when the Scoop bucket cannot be updated. This changes the release workflow so the bucket sync is best-effort instead of blocking Forgejo release publication, which is what red-lined run 8499 after #1401. - What changed: make the scoop manifest bump warn-and-skip on missing or failing write auth, and document that behavior. - Why: the bucket is an install-channel side effect; the canonical release and tap bump should not be held hostage by it. - Test/CI: `ward exec test` passed, including the release contract test. closes #1402 ward.workflow: pull-request-and-merge
fix(release): keep scoop bump from blocking release
All checks were successful
test / test (pull_request) Successful in 57s
49eeb7b140
closes #1402
coilyco-ops closed this pull request 2026-07-15 11:47:42 +00:00
All checks were successful
test / test (pull_request) Successful in 57s

Pull request closed

Sign in to join this conversation.
No description provided.