Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CHANGELOG #25

Merged
merged 8 commits into from
May 20, 2024
Merged

Add CHANGELOG #25

merged 8 commits into from
May 20, 2024

Conversation

BigBlueHat
Copy link
Member

@BigBlueHat BigBlueHat commented May 16, 2024

  • Add initial CHANGELOG file.
  • Update CHANGELOG.md to cover v1.0.0.
  • Update CHANGELOG.md to cover v1.0.1.
  • Update CHANGELOG.md to cover v2.0.0.
  • Update CHANGELOG.md to cover v2.0.1.
  • Update CHANGELOG.md to cover v3.0.0.
  • Update CHANGELOG.md for upcoming release.

Fixes #23

Currently lists all versions and describes the v0.0.1 and v0.0.2 releases.
The released/tagged code between v1.0.1 and v2.0.0 does differ considerably.
It is not clear, though, if that is a fault in how v1.0.1 was released, a
change in the release process, or additional editing that happened on the
v2.0.0 headless branch that was tagged...
Doucmented changes I could find through comparision with v2.0.0 download.

None of these changes are in version control due to using detached branches
to tag releases...
@BigBlueHat BigBlueHat requested a review from davidlehn May 16, 2024 15:28
@BigBlueHat BigBlueHat merged commit 09c3245 into main May 20, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a CHANGELOG.md.
2 participants