Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [0.2.2]
## [0.3.0]
Comment on lines 8 to +10
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

According to the 'Keep a Changelog' standard, which this file states it follows, new changes should be added under the [Unreleased] section. When a new version is released, the [Unreleased] section is renamed to the new version number (and the release date is added), and then a new empty [Unreleased] section is added at the top. It seems the changes for this release were tracked under a placeholder version [0.2.2] instead. For future releases, it would be better to accumulate changes under [Unreleased] to fully adhere to the standard.


Multi-domain support, improved configuration handling, group address validation, Thunder upgrade to 0.27.0, and removal of legacy socketmap/Thunder integration.

Expand All @@ -18,7 +18,7 @@ Multi-domain support, improved configuration handling, group address validation,
* Refactor: Remove socketmap handler and thunder integration by @Aravinda-HWK in https://github.com/LSFLK/silver/pull/305


**Full Changelog**: https://github.com/LSFLK/silver/compare/v.0.2.1...v.0.2.2
**Full Changelog**: https://github.com/LSFLK/silver/compare/v.0.2.1...v.0.3.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There's an inconsistency in the version tag format used in the Full Changelog URLs throughout this file. This line uses the v.X.Y.Z format (e.g., v.0.2.1), while older entries use vX.Y.Z (e.g., for version 0.2.0). For better consistency, it would be ideal to standardize on one format. You might consider addressing this for all URLs in a separate, dedicated PR.


## [0.2.1]

Expand Down
Loading