Release workflow: support manual dry-run builds via workflow_dispatch
Open
Nobody has claimed this yet.
enhancement
priority: low
triage: needs-decision
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 30
Description
Follow-up extracted from closed-out review of PR #31.
Goal
Allow maintainers to run release build validation manually from a branch without publishing an actual tagged release.
Scope
- add
workflow_dispatchtrigger to the release workflow (or a dedicated dry-run workflow) - build the same release artifacts used for tagged releases
- do not publish a GitHub Release when running in manual dry-run mode
- make it obvious in logs/artifacts that this was a dry-run
Success criteria
- maintainer can trigger a release build manually from GitHub Actions
- build produces the expected artifacts for supported targets
- manual dry-run does not publish or mutate release metadata
- tagged releases continue to behave unchanged
Context: PR #31 is mostly already reflected in master; this issue preserves the one notable leftover.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the repository's release workflow and compare it with the behavior preserved from PR #31. Add a manual GitHub Actions entry point that builds the same supported-target artifacts, clearly marks the run as a dry-run, and skips release publication or metadata changes; verify that tagged releases remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 66/100