Skip to content

devops: drop self-hosted Gemini review workflow; pin CI runners - #31

Closed
saucam wants to merge 1 commit into
mainfrom
devops/ci-oss-standards
Closed

saucam wants to merge 1 commit into
mainfrom
devops/ci-oss-standards

Conversation

@saucam

@saucam saucam commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

Post-transfer CI alignment for the public OSS repo.

Removes self-hosted gemini-review.yml — AI review now via org apps (highflame-oracle + gemini-code-assist) + Socket, like other Highflame repos. Also clears the cancel-in-progress review-cancel noise.

Pins CI + release-plz runners → ubuntu-24.04. Left release.yml on ubuntu-latest on purpose — bumping the linux builder raises the glibc floor of the published codeoid-tui binary.

Keeps the OSS-native Rust pipeline (fmt/clippy/nextest+llvm-cov, release-plz + crates.io). Not adopting the private k8s shared workflow (public repo can't use private reusable workflows / self-hosted runners; ships to crates.io, not a cluster).

⚠️ Org-admin: add these repos to highflame-oracle + gemini-code-assist app access.

Co-authored-by: Claude Opus 4.8 (1M context) noreply@anthropic.com

AI review is now the org-level highflame-oracle + gemini-code-assist apps
(+ Socket Security), matching the other Highflame repos, so the self-hosted
`gemini-review.yml` is redundant. Removed.

Pins the CI + release-plz runners to `ubuntu-24.04`. The native-binary build
matrix in release.yml is left on `ubuntu-latest` on purpose — bumping the linux
builder would raise the glibc floor of the published `codeoid-tui` binary.

Keeps the OSS-native Rust pipeline (fmt/clippy/nextest+llvm-cov, release-plz +
crates.io). Deliberately not adopting the private k8s shared workflow.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@saucam saucam closed this Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant