ERROR: There are ZERO commit to release! is thrown when doing a very first release of a package
- Dominant language
- JavaScript
- Stars
- 65
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
### Prerequisites
- [X] I have written a descriptive issue title
- [X] I have searched existing issues to ensure the bug has not already been reported
### Fastify version
x
### Plugin version
x
### Node.js version
16
### Operating system
Linux
### Operating system version (i.e. 20.04, 11.3, 10)
Ubuntu 21.04
### Description
https://github.com/fastify/releasify/blob/e279753300d75f2656837aad07a3a468b4ba91e0/lib/commands/publish.js#L88
### Steps to Reproduce
try to make a very first release of some package by calling
```
releasify publish
```
for example you can check out this one:
https://github.com/nearform/mercurius-apollo-tracing/tree/bab75dee4988e47b0ee776ca21dab1a6f07edc0b
### Expected Behavior
No error is thrown, package get's published
Contributor guide
Research direction
Start at lib/commands/publish.js#L88 and reproduce the failure with `releasify publish` on the mercurius-apollo-tracing example package. Trace how a package with no prior release is handled, then verify that its first release publishes successfully without the zero-commits error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100