semantic-release / semantic-release/commit-analyzer
(Question) Pre-release tag as reference
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
I'm trying to use semantic-release but I want my previous release to be a pre-release (v2.0.0-alpha.1). This tag already exists (no other tags exist). When running semantic-release, the next inferred version is v1.0.0-alpha.1. Any way I can get it to detect the previous tag and to bump to v2.0.0-alpha.2?
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
No source file or test is named. Start by reproducing semantic-release with the existing v2.0.0-alpha.1 tag and inspect how the next version is inferred; done means either inferring v2.0.0-alpha.2 or clearly documenting why that behavior is unsupported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100