Repo still lives under coilysiren while its image publishes to coilyco-bridge #111

New issue

Open

opened 2026-08-12 21:32:32 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-12 21:32:32 +00:00

Collaborator

Observed

The container package is published at
forgejo.coilysiren.me/coilyco-bridge/website, which
coilyco-bridge/deploy pulls. The repository is still at
coilysiren/website. coilyco-bridge/website is a 404 as a repository.

So the image already sits at the post-migration home and the repo did not
follow.

Why it surfaced

coilyco-bridge/deploy reconciles image pins by deriving the source repo from
the image path, which is owner/repo by convention. This repo breaks that
convention, so its pin cannot be watched:

website: forgejo.coilysiren.me/coilyco-bridge/website
         has no resolvable upstream at
         https://forgejo.coilysiren.me/coilyco-bridge/website.git

Before coilyco-bridge/deploy#410 that was
silent. It is now reported by name and deferred every tick, which is better but
still means the deployed pin never advances on its own.

Wanted

Migrate the repository to coilyco-bridge/website so it matches the image and
the rest of the fleet. The image path needs no change, since it is already
correct.

The deploy side needs no change either. Once the repo resolves, the reconciler
picks it up with no further edit.

## Observed The container package is published at `forgejo.coilysiren.me/coilyco-bridge/website`, which `coilyco-bridge/deploy` pulls. The repository is still at `coilysiren/website`. `coilyco-bridge/website` is a 404 as a repository. So the image already sits at the post-migration home and the repo did not follow. ## Why it surfaced `coilyco-bridge/deploy` reconciles image pins by deriving the source repo from the image path, which is `owner/repo` by convention. This repo breaks that convention, so its pin cannot be watched: ``` website: forgejo.coilysiren.me/coilyco-bridge/website has no resolvable upstream at https://forgejo.coilysiren.me/coilyco-bridge/website.git ``` Before https://forgejo.coilysiren.me/coilyco-bridge/deploy/pulls/410 that was silent. It is now reported by name and deferred every tick, which is better but still means the deployed pin never advances on its own. ## Wanted Migrate the repository to `coilyco-bridge/website` so it matches the image and the rest of the fleet. The image path needs no change, since it is already correct. The deploy side needs no change either. Once the repo resolves, the reconciler picks it up with no further edit.

coilyco-ops added the

role/engineer

priority

labels

2026-08-25 08:12:22 +00:00

coilyco-ops added the

autonomy

async-consult

label

2026-08-25 09:31:17 +00:00