Document/automate release process
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Currently running the following command to release:
```sh
lerna publish --force-publish='*' 1.0.0-beta.1
```
- `--force-publish=*` so that all packages always are at the same version, even if one of the packages didn't have any changes.
- `1.0.0-beta.1` for specifying the version to bump to
Things that would be nice to fix:
- [ ] Specify the `--force-publish=*` flag in `lerna.json`
- [ ] Teach Lerna about [emoji-commit](https://github.com/LinusU/emoji-commit), so that the version can be specified automatically
related: https://github.com/LinusU/fanny-pack/issues/1
Contributor guide
No contributing guide indexed for this repository
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 lerna.json and the documented release command, then review the linked emoji-commit project to understand how commit messages could provide the version. Done means the force-publish setting is configured in lerna.json and the release process can determine the version automatically from emoji commits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100