Use semantic-release to automatically publish new versions
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 326
- PR merge metrics
- No merged PRs in 30d
Description
We can follow the pattern from this PR https://github.com/vercel/webpack-asset-relocator-loader/pull/110
However, we will need to set the tagFormat option to omit the v prefix.
And we'll likely have to bump to 1.0.0 in order for semantic-release to work.
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
Review the pattern in PR #110 and the semantic-release tagFormat documentation first. Inspect ncc's existing release configuration and CI setup, then verify that semantic-release publishes new versions without a v prefix and that the project is bumped to 1.0.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100