-
It’s common practice to prefix your version names with the letter
v
. Some good tag names might bev1.0.0
orv2.3.4
. -
If the tag isn’t meant for production use, add a pre-release version after the version name. Some good pre-release versions might be
v0.2.0-alpha
orv5.9-beta
.3.
Syntax: Release <tag>
## Features
- Feature 1: Description of the new feature or functionality added in this release.
- Feature 2: Explanation of another significant feature introduced in this version.
## Enhancements
- Enhancement 1: Description of improvements or optimizations made to existing features.
- Enhancement 2: Overview of enhancements that enhance usability or performance.
## Bug Fixes
- Bug Fix 1: Description of the bug that was fixed and the resolution implemented.
- Bug Fix 2: Explanation of another bug that was addressed and the fix applied.
## Miscellaneous
- Documentation Updates: Briefly mention any updates or additions to the project's documentation.
- Dependency Upgrades: Note any upgraded dependencies or libraries used in the project.
## Contributors
A big thank you to the following contributors who made this release possible:
- QuanBlue (@QuanBlue)
Please refer to the [changelog](https://github.com/QuanBlue/Readme-template) for a complete list of changes and detailed information about each contribution.