Repository navigation
fix(deps): keep go-github on the major ghinstallation uses - #5325
Conversation
The go-github v93 requirement merged in #5314 is unused: the alert publisher still imports v88, which ghinstallation/v2 requires for its token options. Tidy it away and hold go-github majors for Dependency Dashboard approval so a go.mod-only major bump is not proposed again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai full review |
|
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 44 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Breezy! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Readiness at |
Why
The alert publisher uses two libraries that must agree on the GitHub client's major version, and the sign-in library still uses the older one. Automated upgrades to the newer major therefore cannot build: one already merged as an unused leftover, and a second is now red.
What
Removes the unused leftover and makes major upgrades of the GitHub client wait on the dependency bot's dashboard for approval, to be taken together with a sign-in library release on the same major. Minor and patch updates still arrive as before, and this replaces #5321.
No issue: trivial fix.