fix(registry): remove migrated RPG projects from Pipelines #2168

Merged

pipeline-bot merged 1 commit from chore/retire-rpg-registrations into trunk

2026-09-06 13:19:38 +00:00

sean commented

2026-09-06 13:02:44 +00:00

Owner

Change

Remove the four retired RPG PipelineProject declarations and their four disabled PipelineDeliveryPolicy records. This removes rpg-demo, rpg-hello, rpg-lemonade, and rpg-munchers from the Pipelines project list. Binjovi already owns their native Build, Release, Deploy, and reels.

Keep linux and pipelines registered. Keep the pub400-rpg target and ibmi-production environment for historical references. Do not change Build, Release, or Deploy records, object-store files, credentials, hooks, or native branch protections.

Evidence

Red: the updated retirement guard failed on the old rpg-demo registration.
Green: all 152 guards passed in the cluster, strict mode, zero skips. No local tests were run.
Pinned test image: registry.sean.farm/build/pipelines-ci:80c187a5376b@sha256:4f7dd65adea322e1bc0c9ef2537c844887a575f73168e7e266cfe9b0df46b53b.
Live preflight: all 106 old RPG Build/Release/Deploy records have no owner references. No Pipelines-managed RPG children remain for the finalizer to remove.
All 12 native RPG branch/tag protection objects are Flux-owned, without Pipelines labels or owner references.
Native release/deploy proof is complete for rpg-demo v0.1.9, rpg-hello v0.1.8, rpg-lemonade v0.1.8, and rpg-munchers v0.1.5. Current and historical reels were verified before this cleanup.

Delivery

Use the release train with this exact PR only. Do not use a direct Forgejo merge. After main advances, verify pipelines-project-registry sync, two remaining project registrations, all 106 historical record UIDs, and all 12 native protection objects.

## Change Remove the four retired RPG PipelineProject declarations and their four disabled PipelineDeliveryPolicy records. This removes rpg-demo, rpg-hello, rpg-lemonade, and rpg-munchers from the Pipelines project list. Binjovi already owns their native Build, Release, Deploy, and reels. Keep linux and pipelines registered. Keep the pub400-rpg target and ibmi-production environment for historical references. Do not change Build, Release, or Deploy records, object-store files, credentials, hooks, or native branch protections. ## Evidence - Red: the updated retirement guard failed on the old rpg-demo registration. - Green: all 152 guards passed in the cluster, strict mode, zero skips. No local tests were run. - Pinned test image: registry.sean.farm/build/pipelines-ci:80c187a5376b@sha256:4f7dd65adea322e1bc0c9ef2537c844887a575f73168e7e266cfe9b0df46b53b. - Live preflight: all 106 old RPG Build/Release/Deploy records have no owner references. No Pipelines-managed RPG children remain for the finalizer to remove. - All 12 native RPG branch/tag protection objects are Flux-owned, without Pipelines labels or owner references. - Native release/deploy proof is complete for rpg-demo v0.1.9, rpg-hello v0.1.8, rpg-lemonade v0.1.8, and rpg-munchers v0.1.5. Current and historical reels were verified before this cleanup. ## Delivery Use the release train with this exact PR only. Do not use a direct Forgejo merge. After main advances, verify pipelines-project-registry sync, two remaining project registrations, all 106 historical record UIDs, and all 12 native protection objects.

sean added 1 commit

2026-09-06 13:02:44 +00:00