Restore automatic minor publication for dev-base releases #910

New issue

Closed

opened 2026-08-05 21:39:48 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-05 21:39:48 +00:00

Member

Parent: coilysiren/inbox#333

Problem

The promoted dev-base pipeline currently stops after publishing the commit-scoped full-image draft. .forgejo/workflows/release.yml is dispatch-only, so creating the root v* minor release and advancing :release and :latest requires an operator action. Issue #899 is the current instance of that manual gap.

Ward and Agent Compose already publish minor releases automatically after their repository gates pass.

Outcome

Make the existing release workflow callable from the dev-base publisher.
Call it automatically only after the full draft image succeeds.
Keep workflow dispatch for retries, explicit tags, patch overrides, and hand-driven majors.
Queue product-impacting image releases instead of canceling an older in-flight release.
Keep the release and dev-base documentation aligned with the automatic boundary.

Acceptance

A promoted docker/** change builds the draft full image, promotes it to the next root minor tag, advances :release and :latest, and creates the Forgejo release without human dispatch.
A resumed all or full image build completes the same publication chain.
A single-language resume does not create a root release.
Manual release dispatch remains idempotent recovery and override machinery.
Repository validation passes.

Parent: https://forgejo.coilysiren.me/coilysiren/inbox/issues/333 ## Problem The promoted dev-base pipeline currently stops after publishing the commit-scoped full-image draft. `.forgejo/workflows/release.yml` is dispatch-only, so creating the root `v*` minor release and advancing `:release` and `:latest` requires an operator action. Issue #899 is the current instance of that manual gap. Ward and Agent Compose already publish minor releases automatically after their repository gates pass. ## Outcome * Make the existing release workflow callable from the dev-base publisher. * Call it automatically only after the full draft image succeeds. * Keep workflow dispatch for retries, explicit tags, patch overrides, and hand-driven majors. * Queue product-impacting image releases instead of canceling an older in-flight release. * Keep the release and dev-base documentation aligned with the automatic boundary. ## Acceptance * A promoted `docker/**` change builds the draft full image, promotes it to the next root minor tag, advances `:release` and `:latest`, and creates the Forgejo release without human dispatch. * A resumed `all` or `full` image build completes the same publication chain. * A single-language resume does not create a root release. * Manual release dispatch remains idempotent recovery and override machinery. * Repository validation passes.

coilyco-ops referenced this issue from a commit

2026-08-05 21:45:15 +00:00

fix(release): restore automatic dev-base publication, closes #910

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-05 21:45:34 +00:00

fix(release): restore automatic dev-base publication #911

coilyco-ops referenced this issue

2026-08-05 21:53:27 +00:00

interactive: remove the stale-main race from PR AOS CLI tests #913