Skip to content

ci: point workflows at the reusable repo's canonical owner - #131

Merged
leoafarias merged 1 commit into
mainfrom
ci/fix-moved-reusable-workflow-ref
Aug 19, 2026
Merged

ci: point workflows at the reusable repo's canonical owner#131
leoafarias merged 1 commit into
mainfrom
ci/fix-moved-reusable-workflow-ref

Conversation

@leoafarias

Copy link
Copy Markdown
Member

Both CI and publishing are broken here

dart-actions moved from the btwld org to conceptadev. Two workflows still reference the old owner:

file line
ci.yml 11 uses: btwld/dart-actions/.github/workflows/ci.yml@main
release.yml 13 uses: btwld/dart-actions/.github/workflows/publish.yml@main

Why it looks fine but isn't

gh api repos/btwld/dart-actions still returns the repo and its workflows, because the REST API follows rename redirects. That makes the reference look healthy under any manual check.

The Actions reusable-workflow resolver does not follow redirects. The reference is resolved at workflow load, so the entire file is rejected before a single job is created:

error parsing called workflow "..." -> "btwld/dart-actions/..." : workflow was not found

The resulting run is confusing to diagnose: marked failed, referenced_workflows: [], zero jobs, no logs, no annotation exposed through the API, and the run name falls back to the file path. Only the web UI shows the actual error.

We hit exactly this in conceptadev/mix — it silently blocked a release, and it took reading the run page in a browser to find. The comment wording added here matches the note already in conceptadev/naked_ui, which ran into the same trap.

Not yet visible, but imminent

The last CI run here was 2026-08-05, before the move, so nothing has failed yet. The next push to main, the next PR, or the next release tag would have been the first to break — and for a release, that fails after you've already pushed the tag.

Safety

Pure owner rename; no input changes. conceptadev/dart-actions still exposes both ci.yml and publish.yml with an unchanged workflow_call contract — flutter-version, run-dcm, secrets.token for CI, and packages_folder_path / packages for publish. Both files re-parse cleanly.

This PR's own CI run is the verification: if it goes green, the reference resolves.

Deliberately not changed

docs.yml also mentions btwld, at lines 37 and 52 — but those are docs.page and raw.githubusercontent URLs, not uses: references, so they aren't affected by the resolver behavior. Line 37 also asserts against a matching string inside docs/llms.txt.mdx, so changing one without the other would break that check. Worth a separate look if docs hosting needs repointing.

The dart-actions repo moved from the btwld org to conceptadev. GitHub's REST
API follows that rename redirect, so `gh api repos/btwld/dart-actions` still
returns the repo and makes the reference look healthy. The Actions
reusable-workflow resolver does not follow it:

  error parsing called workflow ... "btwld/dart-actions/..." : workflow was not found

The reference is resolved at workflow load, so the whole file is rejected
before any job is created. The run reports failure with zero jobs, no logs, and
no annotation visible through the API -- only the web UI shows the cause.

Both CI and publishing are affected here. The last CI run was 2026-08-05, before
the move, so nothing has failed yet; the next push or release tag would have
been the first to break.

Inputs are unchanged: conceptadev/dart-actions still exposes ci.yml and
publish.yml with the same workflow_call contract (flutter-version, run-dcm,
secrets.token / packages_folder_path, packages).

Comment wording matches the note already added to conceptadev/naked_ui, which
hit this same trap.

The btwld URLs in docs.yml are left alone: they are docs.page and
raw.githubusercontent links, and line 37 asserts against a matching string in
docs/llms.txt.mdx, so changing one without the other would break that check.
@leoafarias
leoafarias merged commit bc37260 into main Aug 19, 2026
1 check passed
@leoafarias
leoafarias deleted the ci/fix-moved-reusable-workflow-ref branch August 19, 2026 23:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant