Skip to content

CD failed on main: run 31391360840 #1150

Closed

Description

@github-actions

CD failed on main: run 31391360840 for commit 16da9393c7fda53390350b5a7bbb20726e2787da (entered via push).

No complete image set was published - publication is all-or-nothing, so every self-updating install stays on the PREVIOUS image until a CD run promotes the full set. Triage the failed job in the linked run. The 3-hourly reconciler will re-attempt main's HEAD on its own (bounded at 3 attempts per commit, logged here); you do NOT need to force a merge to trigger delivery. Close this issue once CD is green.

Activity

  1. added
    ci-failureA main-branch CD run failed - no deployable image was published
    on Aug 10, 2026
  2. rbuergi commented on Aug 10, 2026

    @rbuergi
    Contributor

    Closing — CD recovered and has published complete sets since.

    Two successful CD runs followed the one this issue names (13:12Z and 13:21Z), and the images confirm it rather than the tick:

    3.0.0-rc1.ci.2760   <- promoted
    main
    0268860             <- git-SHA co-tag
    

    A promoted version tag only exists once every leg succeeded and promote ran — under the all-or-nothing gate from #1039 each leg pushes only staging-<sha>-<run_id>, which VersionSelect.PlatformVersionTag can never select. So its presence is itself evidence the set was complete.

    Reopen if it recurs; verify-images now names which image is missing rather than alerting generically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ci-failureA main-branch CD run failed - no deployable image was published

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions