diff --git a/CHANGELOG.md b/CHANGELOG.md index a62b16f0d..29f5f6848 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,13 @@ # Upcoming +### Deprecations + +### Features + +### Bug fixes + +### Improvements + ## v0.6.1 (August 30, 2024) ### Bug fixes diff --git a/docs/developer_guide/making_a_release.rst b/docs/developer_guide/making_a_release.rst index cb06a14d9..412a7ad9a 100644 --- a/docs/developer_guide/making_a_release.rst +++ b/docs/developer_guide/making_a_release.rst @@ -7,13 +7,13 @@ A simple to-do list for the Neuroconv release process: - Format and update the changelog. - Ensure correct formatting and add a header to indicate that the changes belong to a specific release and not upcoming ones. - - Example: `Commit Example ` + - Example: `Format Changelog Example `_ 2. **Set the Correct Version for Release**: - The development version (the current code on `main`) should be one patch version ahead of the latest PyPI release and therefore ready for the next step. - If a minor version bump is necessary, change it accordingly. - - Example: `Version Change Example ` + - Example: `Version Change Example `_ 3. **Perform Checks**: @@ -32,4 +32,4 @@ A simple to-do list for the Neuroconv release process: 6. **Bump Version Post-Release**: - To comply with the one patch version ahead policy, bump the version after the release. - - Example: `Post-Release Version Bump ` + - Example: `Post-Release Version Bump `_ diff --git a/pyproject.toml b/pyproject.toml index ae7d6aba3..b40294d25 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta" [project] name = "neuroconv" -version = "0.6.1" +version = "0.6.2" description = "Convert data from proprietary formats to NWB format." readme = "README.md" authors = [