Question: publish canary and version
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36.1k
- Forks
- 2.3k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 50
Description
I'm trying to do lerna publish --canary in my CI/CD
I'm seeing the "number" after "alpha" is not bumped up (look at the 2nd and 3rd are both alpha.1 )
0.1.3-alpha.0+34fcd0a
0.1.3-alpha.1+d9a9ecb
0.1.3-alpha.1+ezacf1c
How can I make sure that everytime the canary publish can bump up the number after alpha ?
0.1.3-alpha.0+{someSHA}
0.1.3-alpha.1+{someSHA}
0.1.3-alpha.2+{someSHA}
0.1.3-alpha.3+{someSHA}
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 reproducing the lerna publish --canary command in a CI/CD environment and inspect how canary versions are calculated across successive publishes. Compare the observed prerelease numbers with the expected alpha sequence and document whether the behavior is a bug or requires a configuration change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100