Feature request: Auto detect first release
See original GitHub issueHi,
Is it possible to detect first release automatically? Possible alternatives if they don’t conflict current features:
- If version is
0.0.0. - If there is no
CHANGELOG.mdor it is empty.
Kind regards,
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Feature request tracking: Guide, tools & best practices - Beamer
Feature requests are feedback forms that customers can fill out to ask for new features or suggest improvements to existing ones.
Read more >[Feature Request] Implement auto cropping via cropdetect #81
I am working on adding this now, and initial version in develop branch. autocrop. I don't have it run on start as I...
Read more >Feature request response email templates - LiveAgent
Feature requests are messages that customers send to inquire about a feature that is not included in your product or service. Receiving feature...
Read more >Feature Requests: How to Collect Them and Engage Users in ...
Feature requests are an important window into your customers desires and priorities. Here's how to make the most of them, and handle the ......
Read more >Feature Request Tracking Software - FeedBear
Feature Request tracking software like FeedBear allows you to manage and prioritize requests and keep customers in the loop.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

in my
package.jsonI had0.0.0, and the logic with--first-releaseis simple: it skips the bump.there’s also no coordination of
package-lock.jsonwithpackage.jsonwhen running--first-release; if I use0.0.0inpackage.jsonand manually change the version to e.g.,0.1.0in preparation for--first-release, it will publish w/o updatingpackage-lock.jsonto0.1.0. at least, I think so–will have to double-check.