devops: drop self-hosted Gemini review workflow; pin CI runners - #5
Merged
Conversation
AI review is now the org-level highflame-oracle + gemini-code-assist apps, matching the other Highflame repos, so the self-hosted `gemini-review.yml` (added in #2) is redundant. Removed. Pins the CI runner to `ubuntu-24.04`. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
akhiljavelin
approved these changes
Jul 23, 2026
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
2 participants
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.
Removes the self-hosted
gemini-review.yml— AI review is now the org-level highflame-oracle + gemini-code-assist apps (+ Socket Security), matching the other Highflame repos. Pins CI runners toubuntu-24.04. Keeps the OSS-native pipeline (npm-OIDC / crates release-plz); deliberately does NOT adopt the private k8s shared workflow (a public repo cannot consume private reusable workflows or the internal self-hosted runners).(Supersedes the earlier PR, which GitHub left in a stuck state — CI events never dispatched.)
Co-authored-by: Claude Opus 4.8 (1M context) noreply@anthropic.com