Clean up the release process
Open
- Dominant language
- JavaScript
- Stars
- 441
- Forks
- 254
- PR merge metrics
- No merged PRs in 30d
Description
The release process is very manual now. We should automate it so that a build is done, committed and tagged.
Contributor guide
Research direction
Start by reviewing the repository's current release and build process, including its package scripts and configuration. Document how builds are produced, committed, and tagged today; the work is done when that flow is automated and repeatable, with the required steps and validation defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100