Skip to content
Snippets Groups Projects
Select Git revision
  • renovate/main-tsx-4.x
  • main default protected
  • renovate/main-vitest-monorepo
  • renovate/main-ghcr.io-renovatebot-base-image-10.x
  • renovate/main-redis-5.x
  • next
  • feat/config-recommended-merge-confidence-badges
  • renovate/main-xmldoc-2.x
  • refactor/pin-new-value
  • feat/36219--git-x509-signing
  • feat/structured-logger
  • hotfix/39.264.1
  • feat/skip-dangling
  • gh-readonly-queue/next/pr-36034-7a061c4ca1024a19e2c295d773d9642625d1c2be
  • hotfix/39.238.3
  • refactor/gitlab-auto-approve
  • feat/template-strings
  • gh-readonly-queue/next/pr-35654-137d934242c784e0c45d4b957362214f0eade1d7
  • fix/32307-global-extends-merging
  • fix/32307-global-extends-repositories
  • 40.60.1
  • 40.60.0
  • 40.59.4
  • 40.59.3
  • 40.59.2
  • 40.59.1
  • 40.59.0
  • 40.58.1
  • 40.58.0
  • 40.57.1
  • 40.57.0
  • 40.56.3
  • 40.56.2
  • 40.56.1
  • 40.56.0
  • 40.55.2
  • 40.55.1
  • 40.55.0
  • 40.54.1
  • 40.54.0
40 results
Compare
user avatar
feat: restart renovation after github error
Rhys Arkins authored 
When 404 or 422 errors are encountered writing updates, Renovate will now restart in an attempt to fix it. Usually this is because branches/PRs have been edited or closed while Renovate is running.

Closes #1299
eb579ff3
History
user avatar eb579ff3
History