coilyco-flight-deck/mcp-beaver

Watch

Migrate ward-mcp image publishing to Forgejo OCI #34

New issue

Closed

opened 2026-07-27 02:41:32 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-27 02:41:32 +00:00

Member

Outcome

Publish ward-mcp to Forgejo OCI from this source repository, stop publishing it to the standalone k3s registry, and hand the proven immutable reference to the deployment owner.

Program authority: coilysiren/inbox#276

Registry inventory: coilyco-flight-deck/infrastructure#653

Consumer rollout: coilyco-bridge/deploy#239

Target

forgejo.coilysiren.me/coilyco-flight-deck/ward-mcp:<immutable-source-tag>

One published runtime serves the AWS SSM, Discord, Forgejo, Glama, SigNoZ, SkillsMP, and Trello MCP deployments. The publisher keeps that shared-runtime contract intact.

Scope

Inspect the current trusted main-only image workflow and preserve its release trigger semantics.
Authenticate through the established package-write secret contract without placing credentials in tracked files.
Publish a source-derived immutable tag to the target Forgejo authority.
Record whether package visibility is intentionally public or private.
Remove active raw registry endpoints, local pull aliases, insecure-registry configuration, tag checks, and dual-publish behavior owned by this repository.
Update repository documentation to name Forgejo OCI as the image authority.
Report the exact immutable image reference on this issue and on deploy#239 before consumer cutover.
Account for the upload-race, staging-space, and request-timeout risks linked from the umbrella when this publisher uses a large or multi-architecture build.

Acceptance

A trusted main workflow publishes the target image to Forgejo OCI.
The issue records proof that the immutable manifest exists.
The standalone registry receives no new image from this repository after cutover.
Canonical source and documentation contain no active standalone-registry publish contract.
Repository validation passes.
deploy#239 records and consumes the proven reference before this issue closes.

Codex, via advisor surface

## Outcome Publish `ward-mcp` to Forgejo OCI from this source repository, stop publishing it to the standalone k3s registry, and hand the proven immutable reference to the deployment owner. Program authority: https://forgejo.coilysiren.me/coilysiren/inbox/issues/276 Registry inventory: https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/issues/653 Consumer rollout: https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/239 ## Target `forgejo.coilysiren.me/coilyco-flight-deck/ward-mcp:<immutable-source-tag>` One published runtime serves the AWS SSM, Discord, Forgejo, Glama, SigNoZ, SkillsMP, and Trello MCP deployments. The publisher keeps that shared-runtime contract intact. ## Scope * Inspect the current trusted main-only image workflow and preserve its release trigger semantics. * Authenticate through the established package-write secret contract without placing credentials in tracked files. * Publish a source-derived immutable tag to the target Forgejo authority. * Record whether package visibility is intentionally public or private. * Remove active raw registry endpoints, local pull aliases, insecure-registry configuration, tag checks, and dual-publish behavior owned by this repository. * Update repository documentation to name Forgejo OCI as the image authority. * Report the exact immutable image reference on this issue and on deploy#239 before consumer cutover. * Account for the upload-race, staging-space, and request-timeout risks linked from the umbrella when this publisher uses a large or multi-architecture build. ## Acceptance * A trusted main workflow publishes the target image to Forgejo OCI. * The issue records proof that the immutable manifest exists. * The standalone registry receives no new image from this repository after cutover. * Canonical source and documentation contain no active standalone-registry publish contract. * Repository validation passes. * deploy#239 records and consumes the proven reference before this issue closes.  Codex, via advisor surface

coilyco-ops added the

autonomy

async-consult

priority

labels

2026-07-29 03:47:43 +00:00

coilyco-ops commented

2026-07-30 07:53:07 +00:00

Author

Member

OCI migration acceptance is complete.

Main run 53 passed gate and publish for source 51707ba5af.
The AWS SSM, Discord, Forgejo, Glama, SigNoZ, SkillsMP, and Trello Deployment objects consume immutable Forgejo ward-mcp images.
deploy#239 recorded the consumer migration and is closed.
The standalone registry is no longer the source or deployment image authority for Ward MCP.

Current pod availability is separately affected by node.kubernetes.io/disk-pressure. That does not change the completed OCI publisher and consumer cutover.

Successful run: https://forgejo.coilysiren.me/coilyco-flight-deck/ward-mcp/actions/runs/53

OCI migration acceptance is complete. * Main run 53 passed gate and publish for source 51707ba5afeb38ef03605a85012bb72b49b0d8f9. * The AWS SSM, Discord, Forgejo, Glama, SigNoZ, SkillsMP, and Trello Deployment objects consume immutable Forgejo ward-mcp images. * deploy#239 recorded the consumer migration and is closed. * The standalone registry is no longer the source or deployment image authority for Ward MCP. Current pod availability is separately affected by node.kubernetes.io/disk-pressure. That does not change the completed OCI publisher and consumer cutover. Successful run: https://forgejo.coilysiren.me/coilyco-flight-deck/ward-mcp/actions/runs/53

coilyco-ops closed this issue

2026-07-30 07:53:13 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/mcp-beaver#34

No description provided.

Rows
Columns