Conversation
| datasource | package | from | to | | ---------- | ------------------------------- | ------- | ------- | | go | github.com/google/go-github/v72 | v72.0.0 | v81.0.0 | Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
b4e92e1 to
643f0da
Compare
itsmylife
approved these changes
Jan 9, 2026
itsmylife
added a commit
that referenced
this pull request
Feb 12, 2026
…ng (#629) ## Summary Fixes a nil pointer dereference panic caused by the interaction between go-github v81's `ErrorResponse.Is` and the SDK's `guessErrorStatus` function. go-github v76 (bumped from v72 to v81 in #574) changed `ErrorResponse.Is` from a simple type assertion to calling `errors.As(target, &v)` on the target. See PR: google/go-github#3739 The SDK's `guessErrorStatus` (`backend/status.go:112`) passes typed nil targets (`(*url.Error)(nil)`) to `errors.Is`. When `errors.Is` walks the error chain and reaches `*github.ErrorResponse`, the v81 `ErrorResponse.Is` calls `errors.As` on that typed nil, which tries to call `Unwrap()` on the nil receiver — causing a nil pointer dereference panic. The fix adds `sanitizeGitHubError` which converts `*github.ErrorResponse` to a plain error at the `addErrorSourceToError` boundary, preserving the error message while stripping the problematic `Is` method from the error chain. ## Manual reproduction steps 1. Run Grafana with the github-datasource plugin (v2.5.0) 2. Configure the GitHub datasource with a valid personal access token 3. Open Explore (or create a panel) and select the GitHub datasource 4. Set query type to **Workflows** (or **Code Scanning**) 5. Set **Owner** to `grafana`, **Repository** to `this-repo-does-not-exist` 6. Run the query 7. Observe the panic in Grafana server logs: `panic triggered error="runtime error: invalid memory address or nil pointer dereference"` With this fix applied, the query returns a proper error response instead of panicking. Fixes grafana/oss-big-tent-squad#183
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v72.0.0→v81.0.0Release Notes
google/go-github (github.com/google/go-github/v72)
v81.0.0Compare Source
This release contains the following breaking API changes:
BREAKING CHANGE:
UsageItem.Quantityis now typefloat64.PullRequestRuleParameters.AutomaticCopilotCodeReviewEnabledfield (#3866)BREAKING CHANGE:
PullRequestRuleParameters.AutomaticCopilotCodeReviewEnabledis now removed.BREAKING CHANGE:
SCIMEnterpriseDisplayReference.Refis now of type*string.BREAKING CHANGE:
CopilotCodeReviewRuleParameters.ReviewNewPushesis nowReviewOnPush.BREAKING CHANGE:
AddProjectItemOptionsfields have changed types.BREAKING CHANGE:
UpdateRepositoryRulesetClearBypassActor,UpdateRepositoryRulesetClearBypassActor,UpdateRulesetClearBypassActor, andUpdateRulesetNoBypassActorhave been removed as they are no longer needed....and the following additional changes:
PushEvent(#3880)v80.0.0Compare Source
This release contains the following breaking API changes:
BREAKING CHANGE:
ListProvisionedSCIMGroupsEnterpriseOptionsoptional fields are now pointers....and the following additional changes:
structfieldlinter to check struct field names and tags (#3843)v79.0.0Compare Source
This release contains the following breaking API changes:
BREAKING CHANGE:
UpdateProjectItemOptions.Fieldis now[]*ProjectV2FieldUpdate.BREAKING CHANGES: Several
OrganizationsServicemethods have been renamed for better consistency.BREAKING CHANGE:
SCIMService.ListSCIMProvisionedGroupsForEnterpriseis nowEnterpriseService.ListProvisionedSCIMEnterpriseGroups....and the following additional changes:
required_reviewerssupport toPullRequestRuleParameters(#3806)jsonfieldnamelinter to support$injsontag names (#3826)v78.0.0Compare Source
This release contains the following breaking API changes:
BREAKING CHANGES: Various
EnterpriseServicestructs have been renamed for consistency....and the following additional changes:
sha_pinning_requiredtoActionsPermissionsstructs (#3807)v77.0.0Compare Source
This release contains the following breaking API changes:
BREAKING CHANGE:
RepositoriesService.CreateStatusnow takes value forstatus, not pointer.BREAKING CHANGES:
ProjectV2Field.Optionschanged from[]anyto[]*ProjectV2FieldOption.ProjectV2Field.URLis nowProjectV2Field.ProjectURLProjectV2structs are now passed as pointersProjectsServicefunctions with #3761...and the following additional changes:
Authorizationwhentokenis available (#3789)v76.0.0Compare Source
This release contains the following breaking API changes:
BREAKING CHANGE: ActionsBilling endpoints are removed.
GetRepositoriesForCodeSecurityConfiguration(#3707)BREAKING CHANGE: GetRepositoriesForCodeSecurityConfiguration now returns RepositoryAttachment instead of Repository.
BREAKING CHANGE: Permissions-related methods are renamed from
Edit*toUpdate*.BREAKING CHANGE:
GetDefaultCodeSecurityConfigurationsnow returnsCodeSecurityConfigurationWithDefaultForNewReposinstead ofCodeSecurityConfiguration.BREAKING CHANGE: Billing-related methods are renamed to pattern, and required fields are changed to value types.
...and the following additional changes:
v75.0.0Compare Source
This release contains the following breaking API changes:
BREAKING CHANGE:
GitServicemethods now pass required params by-value instead of by-ref....and the following additional changes:
v74.0.0Compare Source
This release contains the following breaking API changes:
BREAKING CHANGE:
ListSCIMProvisionedGroupsForEnterprisenow takesListSCIMProvisionedGroupsForEnterpriseOptionsinstead of*ListSCIMProvisionedIdentitiesOptions.BREAKING CHANGE: Change
ListCheckSuiteOptions.AppIDfrominttoint64...and the following additional changes:
v73.0.0Compare Source
This release contains the following breaking API changes:
BREAKING CHANGE:
ListCustomPropertyValuesnow takesListCustomPropertyValuesOptionsinstead ofListOptions....and the following additional changes:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.