bvandeusen/minstrel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 38 Wiki Activity

ci(release): add workflow_dispatch + docker diagnostics #2

Merged
bvandeusen merged 262 commits from dev into main 2026-04-18 19:21:18 -04:00
Conversation 0 Commits 262 Files Changed 299
+27003
bvandeusen commented 2026-04-18 19:19:17 -04:00 (Migrated from git.fabledsword.com)
Copy Link
Copy Source

Summary

Release workflow run #25 failed post-merge with the Docker build/push steps. To diagnose without needing a fresh commit each time, this PR:

  • Adds workflow_dispatch: so release.yml can be re-run from the Forgejo UI or MCP on any merge state.
  • Prepends a docker environment diagnostics step that dumps id, DOCKER_HOST, the docker.sock listing, docker version/info, and docker buildx version/ls before any build or login runs. Lets us see exactly what the job container sees.

Merging this will also re-trigger release.yml with the new diagnostics, which should tell us whether the runner's docker socket is mounted + reachable.

Test plan

  • CI lane (test.yml) still passes on dev after this change (syntax-only addition to release.yml)
  • Post-merge: release run produces readable diagnostic output we can act on
  • Follow-up (same PR cycle) once the build fix is known and applied: :main image lands in the Forgejo registry (closes Fable task 281)
## Summary Release workflow run #25 failed post-merge with the Docker build/push steps. To diagnose without needing a fresh commit each time, this PR: - Adds `workflow_dispatch:` so `release.yml` can be re-run from the Forgejo UI or MCP on any merge state. - Prepends a **docker environment diagnostics** step that dumps `id`, `DOCKER_HOST`, the `docker.sock` listing, `docker version/info`, and `docker buildx version/ls` before any build or login runs. Lets us see exactly what the job container sees. Merging this will also re-trigger release.yml with the new diagnostics, which should tell us whether the runner's docker socket is mounted + reachable. ## Test plan - [x] CI lane (`test.yml`) still passes on dev after this change (syntax-only addition to release.yml) - [ ] Post-merge: release run produces readable diagnostic output we can act on - [ ] Follow-up (same PR cycle) once the build fix is known and applied: `:main` image lands in the Forgejo registry (closes Fable task 281)
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
deps
Dependency update (Renovate)
 deps:major
Major dependency bump — held for manual review
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bvandeusen
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bvandeusen/minstrel#2
Delete Branch "dev"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?