ci: stop publishing oikos and claim-forge images - #57
Merged
Conversation
Follow-up to the earlier trust-pipeline-images cleanup. Two more services were still built and pushed (now also with build-provenance attestations) under odds-and-sods, mis-attributing their GHCR packages: oikos -> belongs to hyperpolymath/oikosbot (relink the package there) claim-forge -> part of a private system; must not be published publicly here Both are removed from the build matrix. cerro-torre is the only service still built here, pending confirmation it has no upstream or private home of its own. Note: oikos/claim-forge are still referenced by trust-pipeline-e2e.yml, selur-compose.yml and OPSM core; deleting their packages needs a separate pass to strip those references (same applies to the retired cicd-hyper-a). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J88oVkzkSn8DyHx3zxKeXS
hyperpolymath
marked this pull request as ready for review
June 26, 2026 12:11
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.
Why
Follow-up to #50. Two more services were still built and pushed (now also with build-provenance attestations from #55) under odds-and-sods, mis-attributing their GHCR packages:
oikos→ belongs tohyperpolymath/oikosbot; the package should be relinked there.claim-forge→ part of a private system; it must not be published as a public OPSM package (its sourceservices/claim-forge/is also public in this repo — see "open items").docker/metadata-actioninjectsorg.opencontainers.image.sourcefrom the repo running the build, so anything built here links to odds-and-sods regardless of where it really belongs.What
Removes
oikosandclaim-forgefrom thetrust-pipeline-imagesbuild matrix.cerro-torreis now the only service still built here — flagged in-file pending confirmation it has no upstream/private home of its own.This is self-contained:
trust-pipeline-e2e.ymlpulls these images (it doesn't depend on the build job), so trimming the matrix doesn't break e2e.Manual GHCR steps (API can't do these)
oikos: Package → settings → unlink (🗑) → relink tooikosbot.claim-forge: delete the public package (and decide on the public source — see below).Open items / follow-ups
services/claim-forge/is a real 229-line public Rust service in this public repo. If it's meant to be private, the source needs removing too, not just the package.oikos/claim-forge/cicd-hyper-aare still referenced bytrust-pipeline-e2e.yml,selur-compose.ymland OPSM core. Deleting theclaim-forge/cicd-hyper-apackages needs a separate pass to strip those references first, or e2e CI will fail to pull them.🤖 Generated with Claude Code
https://claude.ai/code/session_01J88oVkzkSn8DyHx3zxKeXS
Generated by Claude Code