Skip to content

bip174: update changelog for semver/consistency#2145

Open
jonatack wants to merge 1 commit intobitcoin:masterfrom
jonatack:2026-04-bip174-semver
Open

bip174: update changelog for semver/consistency#2145
jonatack wants to merge 1 commit intobitcoin:masterfrom
jonatack:2026-04-bip174-semver

Conversation

@jonatack
Copy link
Copy Markdown
Member

@jonatack jonatack commented Apr 15, 2026

following up on #2135 (comment).

Per https://semver.org/:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes
MINOR version when you add functionality in a backward compatible manner
PATCH version when you make backward compatible bug fixes

Per https://keepachangelog.com/en/1.0.0/:

Changelogs are for humans.

Should you ever rewrite a changelog?

Sure. There are always good reasons to improve a changelog.

@jonatack jonatack added the Metadata Update Changes to Changelog or Preamble without changing the technical content of a BIP. label Apr 15, 2026
@jonatack jonatack force-pushed the 2026-04-bip174-semver branch from fe49d00 to 02dc9b1 Compare April 15, 2026 19:16
@murchandamus
Copy link
Copy Markdown
Member

I am not convinced that a metadata update like a Status advancement warrants a bump of MINOR, also see: #2143 (comment)

@jonatack
Copy link
Copy Markdown
Member Author

I think a status update is reasonably significant.

For instance, "Version 1.0.0 is used for promotion to Complete" -- so it arguably doesn't make sense that the other status updates would be patch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Metadata Update Changes to Changelog or Preamble without changing the technical content of a BIP.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants