Add a concurrency guard to the Renovate workflow #43

New Issue

2026-06-16T14:42:59+01:00

lyrathorpe commented

2026-06-16 14:42:59 +01:00

Problem

The Renovate workflow runs on both @hourly and push: main with no concurrency
control. Overlapping runs do autodiscover simultaneously, producing duplicate PRs
and extra concurrent writes against Gitea — which aggravates the
ErrIssueAlreadyChanged 500s seen when merging.

Fix

concurrency:
  group: renovate
  cancel-in-progress: false

## Problem The Renovate workflow runs on both `@hourly` and `push: main` with no concurrency control. Overlapping runs do autodiscover simultaneously, producing duplicate PRs and extra concurrent writes against Gitea — which aggravates the `ErrIssueAlreadyChanged` 500s seen when merging. ## Fix ```yaml concurrency: group: renovate cancel-in-progress: false ```

lyrathorpe referenced a pull request that will close this issue

2026-06-16 14:43:53 +01:00

ci(renovate): serialize runs, quiet logs, clean config-file env #51

lyrathorpe referenced this issue from a commit

2026-06-16 14:43:54 +01:00

ci(renovate): serialize runs, quiet logs, clean config-file env

lyrathorpe closed this issue

2026-06-16 14:51:51 +01:00

Sign in to join this conversation.