rust-lang / rust-lang/rust-analyzer
Prevent publishing a release when a subtask fails?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Last nightly release doesn't contain a vscode extension file because "publish release" task was interrupted (for whatever reason): https://github.com/rust-analyzer/rust-analyzer/runs/2210499132?check_suite_focus=true
But the release still succeeded and broke update of the extension for nightly users.
Shouldn't the whole release process fail when one of the release subtasks fails though? 🤔
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
Start with the linked GitHub Actions run and inspect the release workflow around the interrupted “publish release” task. Trace how subtask failures are propagated to the overall release result. Done means a failed release subtask causes the whole release process to fail instead of publishing an incomplete release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100