Skip to content

chore(deps): update go-github to v90 - #159

Open
dsimansk wants to merge 1 commit into
openshift:masterfrom
dsimansk:srvocf-1053-go-github-v90
Open

chore(deps): update go-github to v90#159
dsimansk wants to merge 1 commit into
openshift:masterfrom
dsimansk:srvocf-1053-go-github-v90

Conversation

@dsimansk

Copy link
Copy Markdown

Bump github.com/google/go-github from v72 to v90.

The v90 major release replaces the fluent client constructor with functional options and changes several method signatures. Adapt the GitHub SCM client accordingly:

  • build the client via NewClient(WithHTTPClient, WithAuthToken, WithURLs) instead of NewClient(...).WithAuthToken(...) and a settable BaseURL field
  • pass Commit and Blob by value to CreateCommit and CreateBlob
  • call UpdateRef with the ref string and an UpdateRef body
  • call CreateOrUpdateRepoSecret with the secret name and a SecretRequest body

Add a branchRef helper so the GetRef and UpdateRef call sites share one ref string; go-github provides no such helper.

Summary

  • chore(deps): update go-github to v90

Fixes SRVOCF-1053

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 24, 2026
@dsimansk
dsimansk force-pushed the srvocf-1053-go-github-v90 branch from 12276db to a2d5084 Compare August 24, 2026 16:03
@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 24, 2026
Bump github.com/google/go-github from v72 to v90.

The v90 major release replaces the fluent client constructor with
functional options and changes several method signatures. Adapt the
GitHub SCM client accordingly:

- build the client via NewClient(WithHTTPClient, WithAuthToken,
  WithURLs) instead of NewClient(...).WithAuthToken(...) and a
  settable BaseURL field
- pass Commit and Blob by value to CreateCommit and CreateBlob
- call UpdateRef with the ref string and an UpdateRef body
- call CreateOrUpdateRepoSecret with the secret name and a
  SecretRequest body

Add a branchRef helper so the GetRef and UpdateRef call sites share
one ref string; go-github provides no such helper.

Issue SRVOCF-1053

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@dsimansk
dsimansk force-pushed the srvocf-1053-go-github-v90 branch from a2d5084 to c18df08 Compare August 24, 2026 16:05
@dsimansk

Copy link
Copy Markdown
Author

/test e2e-aws

@openshift-ci
openshift-ci Bot requested review from matejvasek and twoGiants August 24, 2026 16:05
@openshift-ci openshift-ci Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 24, 2026
@openshift-ci

openshift-ci Bot commented Aug 24, 2026

Copy link
Copy Markdown

@dsimansk: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@pmeida pmeida left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 25, 2026
@openshift-ci

openshift-ci Bot commented Aug 25, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pmeida

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants