ci: manual Aminet upload workflow for failed-publish recovery - #15
Merged
Conversation
When the automated Aminet upload in release.yml fails for a transient
reason (FTP timeout, Aminet maintenance window, whatever) you
currently have to either:
- retag and re-run the whole release flow, which also re-publishes
the GitHub Release with a duplicate of an already-good artefact, or
- drop down to a shell and run lftp by hand against main.aminet.net.
Neither is great. Add a workflow_dispatch-triggered job that takes a
tag input, downloads the versioned lha + readme from that GitHub
Release, renames them to the Aminet-shape unversioned form, and runs
the same sidick/aminet-release-action that release.yml uses.
Usage:
gh workflow run "Aminet upload (manual)" -f tag=v44.0
or click "Run workflow" in the Actions tab UI.
Implementation notes baked into the YAML comments:
- The action's "attach to matching GitHub Release" step short-circuits
on workflow_dispatch because GITHUB_REF is the branch, not the tag.
Exactly what we want -- the release page already has its assets.
- Files must land inside $GITHUB_WORKSPACE because the action runs in
Docker and only the workspace is bind-mounted.
- Permissions: contents: read is enough; we never write to the
release or to the repo.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A new
.github/workflows/aminet-upload.ymltriggered byworkflow_dispatch(manual button in the Actions tab, orgh workflow run). Takes a tag input, downloads the versioned lha + readme from that GitHub Release, renames to the unversioned Aminet shape, runs the samesidick/aminet-release-action@v1.Why
When the automated upload in
release.ymlfails for a transient reason (FTP timeout, Aminet maintenance, etc.) the current recovery options are:Neither is great. This workflow retries just the Aminet step against an existing release.
Usage
Or from the GitHub UI: Actions → "Aminet upload (manual)" → Run workflow → enter the tag.
Implementation notes
workflow_dispatchbecauseGITHUB_REFis the dispatched branch, not the tag. Confirmed by reading the action's_attach_to_releasesource. Good -- the release page already has its assets, we don't want to re-attach.$GITHUB_WORKSPACE(viabuild/and the repo root) so the action's Docker container can see them; only the workspace is bind-mounted.permissions: contents: readis sufficient -- the workflow never writes to the release or to the repo.Validation
The three existing CI jobs (host-build, amiga-dist, semgrep) run as usual on this PR -- they don't touch the new workflow. The new workflow itself can only be validated by manually running it after merge against an existing release. Plan: trigger
gh workflow run "Aminet upload (manual)" -f tag=v44.0once merged and watch the log. If there's a bug, fix forward in a follow-up PR.