When making changes to the codebase, always update the CHANGELOG.md file to reflect the modifications:
- Add new entries under the
## [Unreleased]section - Follow the Keep a Changelog format
- Use these categories as appropriate:
### Features- for new features### Fixes- for bug fixes### Breaking Changes- for breaking API changes### Deprecated- for soon-to-be removed features### Removed- for removed features### Security- for security fixes
- Use bullet points starting with
-for each change - Keep descriptions concise but clear
- When a version is released, the maintainer will move unreleased items to a dated version section
Example entry:
## [Unreleased]
### Features
- Add new --parallel option for concurrent test execution
### Fixes
- Fix race condition in test output handlingTo make a new release, perform the following steps:
- Update the package version in package.json
- Run npm install to automatically update package-lock.json
- Update Changelog.md with the new version
- Commit the above changes
- Run
./check-publishand make sure that it succeeds - push master
- Create a git tag in the format
v1.2.3 - Push the tag