Reverse #543 and migrate dev-base consumers to the single :release tag #643

New issue

Closed

opened 2026-07-25 06:18:04 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-25 06:18:04 +00:00

Member

Decision

Reverse #543. The fleet no longer pins AOS dev-base consumers to versioned container tags. Every managed consumer moves to:

forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:release

:release is the single supported consumer tag. Storage containment is the priority. This issue owns the consumer-side migration first, before coilyco-flight-deck/agentic-os#739 removes publisher-side tag and package churn.

Scope

Change the infrastructure dev-harness default from its versioned image tag to :release, removing the separate tag-pin variable where it no longer carries a useful choice.
Change infrastructure workflows, scripts, examples, and documentation that currently name agentic-os:v* to agentic-os:release.
Change the CI-in-dev-base rollout generator so newly generated or refreshed workflows use :release.
Inventory functional dev-base references across the managed fleet and migrate versioned, :latest, and retired tier tags to :release in each owning repository through its normal landing workflow.
Reverse documentation that requires an exact published dev-base version. Document the moving :release contract as intentional.
Record the final zero-consumer inventory on this issue so AOS#739 can remove the old publication surfaces safely.

Boundary

This issue changes consumers and rollout policy. AOS#739 owns the publisher change that leaves only the single :release tag.
Infrastructure#600 owns registry retention and supported package cleanup.
This issue performs no direct registry, database, or filesystem deletion.
This issue does not introduce an alternative pin, candidate tag, rollback tag, digest-pinning scheme, or cache-policy redesign.

Acceptance

Infrastructure's dev-harness role pulls forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:release with no version-tag default.
Every functional dev-base reference in infrastructure uses :release.
The managed fleet inventory contains no functional consumer of agentic-os:v*, agentic-os:latest, or a retired tier tag. Local-only build tags are excluded.
The rollout generator emits :release.
A representative infrastructure workflow and dev-harness converge pull :release successfully.
Each changed repository passes its normal validation and lands through its resolved workflow.
The issue thread records the final inventory and links the AOS#739 publisher handoff.

References

## Decision Reverse #543. The fleet no longer pins AOS dev-base consumers to versioned container tags. Every managed consumer moves to: `forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:release` `:release` is the single supported consumer tag. Storage containment is the priority. This issue owns the consumer-side migration first, before `coilyco-flight-deck/agentic-os#739` removes publisher-side tag and package churn. ## Scope * Change the infrastructure dev-harness default from its versioned image tag to `:release`, removing the separate tag-pin variable where it no longer carries a useful choice. * Change infrastructure workflows, scripts, examples, and documentation that currently name `agentic-os:v*` to `agentic-os:release`. * Change the CI-in-dev-base rollout generator so newly generated or refreshed workflows use `:release`. * Inventory functional dev-base references across the managed fleet and migrate versioned, `:latest`, and retired tier tags to `:release` in each owning repository through its normal landing workflow. * Reverse documentation that requires an exact published dev-base version. Document the moving `:release` contract as intentional. * Record the final zero-consumer inventory on this issue so AOS#739 can remove the old publication surfaces safely. ## Boundary * This issue changes consumers and rollout policy. AOS#739 owns the publisher change that leaves only the single `:release` tag. * Infrastructure#600 owns registry retention and supported package cleanup. * This issue performs no direct registry, database, or filesystem deletion. * This issue does not introduce an alternative pin, candidate tag, rollback tag, digest-pinning scheme, or cache-policy redesign. ## Acceptance * Infrastructure's dev-harness role pulls `forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:release` with no version-tag default. * Every functional dev-base reference in infrastructure uses `:release`. * The managed fleet inventory contains no functional consumer of `agentic-os:v*`, `agentic-os:latest`, or a retired tier tag. Local-only build tags are excluded. * The rollout generator emits `:release`. * A representative infrastructure workflow and dev-harness converge pull `:release` successfully. * Each changed repository passes its normal validation and lands through its resolved workflow. * The issue thread records the final inventory and links the AOS#739 publisher handoff. ## References * #543 * #600 * https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/issues/739 * https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/issues/642

coilyco-ops added the

autonomy

live-collab

priority

labels

2026-07-29 03:46:31 +00:00

coilyco-ops added

priority

and removed

priority

labels

2026-08-05 10:25:56 +00:00