GHES 3.19: HTTP 500 when viewing all PRs created by Renovate in GitHub

[ErikHumphrey]

After updating renovate-ce to 13.1.0 and GitHub Enterprise Server to 3.19.0 (see release notes), I'm experiencing the following catastrophic issues:

• Pull requests created by Renovate are created successfully, but inaccessible in the UI, consistently resulting in an HTTP 500 error. They're still accessible via the API or pull/100.patch or pull/100.diff URLs.
• (timestamp) | Client: (ip) | Status: 500 (Crash) | Time: 595ms | Request: GET (owner/repo)/pull/100
• Thought maybe database schema mismatch, but the column isn't missing.
• Loaded the PR itself by Rails console, and I can load its body, internal id, merge base, SHA, etc. just fine.
• Removing branch protection rules or review requests using the Rails console (not through the UI) temporarily alleviates this issue but branch protection rules must be kept disabled else new PRs will 500

  protection = repo.protected_branches.find_by(name: branch_name)
  protection.destroy 

• Certain Renovate pull requests do not appear in a repo's" Pull requests" search listing but can be loaded if visited directly by link
  • Could be an Elasticsearch indexing issue
• Certain pull requests that are "closed" appear under an is:open search
• The pull requests interface does not load at all in GitHub Mobile (uses GraphQL queries).
  • The HTTP response for this is 200 OK (that's how GraphQL works).
• Jenkins integration with GHES also encounters more issues with PRs than normal, or doesn't create pipelines on PR creation, requiring a manual scan

  Checking pull request #100 Waiting for GitHub to create a merge commit for pull request 100. Retrying 3 more times... FATAL: Failed to recompute children... org.kohsuke.github.HttpException

This could be a GHES bug, but it could also indicate incompatibility between the current version of Renovate and the new version of GHES. As a third-party application, t's outside the scope of GitHub Support.

The error I get in GHES exceptions.log feels like the UI rendering bug / crash to me.

NoMethodError: undefined method 'bot' for nil Location: RuleEngine::PullRequestStrictReviewRule#check_reviews

Attempted fixes

• Comment out CODEOWNERS
• Delete and recreate the organization Team listed in CODEOWNERS
• Check database for corrupted tables, zombie users in teams, etc.
• Delete review requests on the Renovate PRs
• Change commit author of Renovate PRs

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Renovate CE never opening PRs #610
• ignorePrAuthor doesn't affect Bitbucket Server URLs anymore, triggering API errors #781
• All PRs get "Edited/blocked notification" when using MEND_RNV_GITHUB_BOT_USER_ID with Renovate CE #741
• Repository Limit #796

🔗 Related PRs

#609 - fix(ce): Remove unused existingSecret condition for GITHUB_BOT_USER_ID [merged]
mend/renovate-pro-automation#20 - RABC-support [merged]
mend/renovate-unified-repo-automation#139 - Fix broken tests for 25.11.1 [closed]

👤 Suggested Assignees

• KarstenSiemer
• hauerhan
• simonhaenisch
• mcaulifn
• ehumphrey-payments

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[jamietanna]

Pull requests created by Renovate are created successfully, but inaccessible in the UI

To confirm, do you mean the GitHub UI doesn't load the Renovate created PRs?

[ErikHumphrey]

That's right.

After following up with GitHub, they might agree it's a regression on their part, so they're attempting to implement a fix. I'll close the issue in a little while if that resolves it.