standard-version

:trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org

Command Line Developer Tools

Explore on GitHub Read Hacker News discussions

6Distinct people

6Mentions

0Explicit recommenders

8KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

:trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:03:49 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2016-10-23 23:31:22 UTC to 2020-08-19 20:45:32 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	1	1	0
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	0	0	0
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	2	0	2
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	2	0	2
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	0	1

What Hacker News says

2 sources

makepanic·Nov 6, 2018

If one uses a specification for defining changes, then you can easily generate changelogs regardless of IDE/editors. e.g. https://www.conventionalcommits.org/en/v1.0.0-beta.2/ has implementations[1] that generate changelogs and bump package versions. [1] - https://github.com/conventional-changelog/standard-version

In Why I wrote 33 VSCode extensions and how I manage them

tmcw·Jul 28, 2018

As far as I can tell, the autogeneration of changelogs you can do with standard-version https://github.com/conventional-changelog/standard-version and commitzen ( https://github.com/commitizen/cz-cli ) fulfills the criteria Keep a Changelog wants: right date format, clear notes for breaking changes, and no unnecessary information from irrelevant commits. I've really liked using the two for a variety of systems - the strict commit message formatting and opinionated changelog generation means that the resulting changelogs are pretty darn readable. But ymmv.

In Keep a Changelog