Switch to mostly manual release notes #368
Merged
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.
Recreation of #348 because that PR is unmergable due to unresolved comments, even though the PR has no unresolved comments 🐛 .
Summary
This PR introduces a
CHANGELOG.md
file to the Hyperlight repository to systematically track and document changes. The goal is for this file to be updated with each PR that contributes to the release notes. However, in practice, it will be manually edited by the individual responsible for creating a Hyperlight release.Motivation
The need for manual release notes arose from the limitations of our automatic release notes system. The current automatic notes were generated from PR titles, which often don't adequately reflect the changes in a manner that's easily consumable by users.
Changes
CHANGELOG.md
file has been added to document key changes.CHANGELOG.md
and a full list of PRs with their titles at the end of the release notes.This approach draws inspiration from the release notes format used by Runwasi, as seen in this example.
After this merges, I will replace the old release notes in 0.2.0 with the new ones