conventional-changelog/standard-version

Feature request: Auto detect first release

Open

#365 opened on May 22, 2019

View on GitHub
 (6 comments) (2 reactions) (0 assignees)JavaScript (7,442 stars) (825 forks)batch import
feature-requesthelp wanted

Description

Hi,

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.md or it is empty.

Kind regards,

Contributor guide

Tech stack
javascriptnodejs
Domain
clireleasedeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
nodejsgitconventional commits
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate how standard version currently determines the initial release. Examine the version detection logic in the codebase, possibly in files like `lib/lifecycles/bump.js` or `lib/run.js`. Check if there are any existing checks for version `0.0.0` or missing CHANGELOG.md. The issue suggests two alternatives; evaluate their feasibility and any potential conflicts. Look at related issues or PRs for context.