Add CHANGELOG with 0.1.0 release #4
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rnestler
reviewed
Feb 4, 2024
Member
rnestler
left a comment
rnestler
left a comment
There was a problem hiding this comment.
I use https://keepachangelog.com/en/1.1.0/ for changelogs, but I'm OK with this format as well.
Contributor
Author
I use that for some projects as well (those with more activity), but I think for small projects with small releases it's a bit overkill 🙂 |
rnestler
force-pushed
the
add-changelog
branch
from
03a49bf to
6a522ed
Compare
rnestler
approved these changes
Dec 29, 2024
Contributor
Author
|
@rnestler you forgot the tag 🙂 see PR description. |
Contributor
Author
I added the tag! (Tags are required for go modules in order to update the dependents to the latest version.) |
Member
|
I've no idea how go dependency management works, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Should be merged after #3, and be immediately followed by a release tag.
@gidsi is this CHANGELOG / format OK for you? Do you have opinions on the version scheme? I'd go to 0.1.0 for this release. After that, minor increase for new features and patch increases for bugfixes.
Alternatively, we could also go straight to 1.0.0, since the project is a few years old now, and shouldn't drastically change anymore. (And if it does, we can always bump to 2.x)