Skip to content

ci: mirror.yml — mirror-radicle job fails (needs upstream investigation at hyperpolymath/standards) #268

Description

@hyperpolymath

Finding

`.github/workflows/mirror.yml` calls `hyperpolymath/standards/.github/workflows/mirror-reusable.yml@e6b2884`. The `mirror-radicle` job inside the reusable fails reliably; the other 6 targets (gitlab, sourcehut, disroot, bitbucket, codeberg, gitea) get cancelled by fail-fast.

What the log shows

Failed step `Mirror to Radicle` exit code is masked behind GitHub Actions teardown noise. The truncated log shows only `Cleaning up orphan processes` after the step completes; the actual failure output is not exposed.

Common causes for Radicle CLI failure in CI:

  1. Missing `RAD_KEY` / authentication secret
  2. Radicle daemon not reachable
  3. CLI flag drift between Radicle versions

Path forward (upstream, not in-repo)

This is a reusable-workflow problem. The fix lives in `hyperpolymath/standards .github/workflows/mirror-reusable.yml` (or its referenced action setup). Recommend:

  1. File an upstream issue at `hyperpolymath/standards` referencing this finding (would affect all estate repos using this reusable).
  2. In the meantime, this repo's mirror.yml `failure` status is expected red and admin-merge-friendly.

Cross-link

Memory hook `[Estate rust-ci-reusable@cc5a372 = 100% red universal]` documents a similar estate-wide reusable-red pattern — keep the same triage stance for mirror-radicle pending upstream investigation.

Discovered: 2026-06-01 CI/CD audit.

Activity

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

    bugSomething is broken or behaves incorrectlycicdCI/CD: workflows, actions, lockfiles, pins, runners, release gatespriority:p2Normal - queue itscope:estateAffects many or all repos across the estatestatus:blockedCannot proceed until a dependency clears

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions