Discussed in #44408
Originally posted by torstenzyder July 7, 2026
Describe the bug
On GitHub Enterprise Cloud (GHEC), Renovate running as a GitHub App creates a new Dependency Dashboard issue on every run instead of updating the existing one. getIssueList() consistently returns 0 issues, so findIssue("Dependency Dashboard") returns null and ensureIssue() creates a duplicate.
Root cause
getIssues() uses the getIssuesQuery GraphQL query, which filters server-side:
issues(filterBy: { createdBy: $user }) # $user = renovateUsername = "renovate-bot[bot]"
On GHEC, filterBy.createdBy does not match the GitHub App bot login (name[bot]), returning 0 issues, even when the open Dashboard issue's author.login is exactly renovate-bot[bot]. On github.com the same filter matches, so this is GHEC-specific.
PRs are unaffected because they are fetched without a server-side author filter and filtered in code (ghPr.user.login === username).
Confirmation
Reproduced with the latest version. @torstenzyder verified via REST that the existing Dashboard issue's author.login exactly matches the configured username (renovate-bot[bot]), yet the GraphQL query still returns empty. Check linked discussion.
Proposed fix
Mirror the PR path: remove the createdBy filter from getIssuesQuery, add author { login } to the issue node, and filter issues in code by author.login === renovateUsername
Discussed in #44408
Originally posted by torstenzyder July 7, 2026
Describe the bug
On GitHub Enterprise Cloud (GHEC), Renovate running as a GitHub App creates a new Dependency Dashboard issue on every run instead of updating the existing one.
getIssueList()consistently returns 0 issues, sofindIssue("Dependency Dashboard")returns null andensureIssue()creates a duplicate.Root cause
getIssues()uses thegetIssuesQueryGraphQL query, which filters server-side:issues(
filterBy: { createdBy: $user })# $user = renovateUsername = "renovate-bot[bot]"On GHEC,
filterBy.createdBydoes not match the GitHub App bot login (name[bot]), returning 0 issues, even when the open Dashboard issue'sauthor.loginis exactlyrenovate-bot[bot]. On github.com the same filter matches, so this is GHEC-specific.PRs are unaffected because they are fetched without a server-side author filter and filtered in code (
ghPr.user.login === username).Confirmation
Reproduced with the latest version. @torstenzyder verified via REST that the existing Dashboard issue's
author.loginexactly matches the configured username (renovate-bot[bot]), yet the GraphQL query still returns empty. Check linked discussion.Proposed fix
Mirror the PR path: remove the
createdByfilter fromgetIssuesQuery, add author { login } to the issue node, and filter issues in code byauthor.login === renovateUsername