Should we implement automated releases?
Open
Nobody has claimed this yet.
pinned
Question
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 809
- PR merge metrics
- No merged PRs in 30d
Description
#1656 was caused by me overlooking a manual step when preparing the release.
This has likely happened before, and will likely happen again.
I think we should consider implementing automated releases of some sort.
Ideas
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 by reviewing issue #1656 and the semantic-release proposal linked in this issue. Define the release steps that should be automated and what evidence would show that the current manual omission can no longer occur; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100