version bumpb

CHANGELOG.md

@@ -1,5 +1,13 @@
 # Upcoming
 
+### Deprecations
+
+### Features
+
+### Bug fixes
+
+### Improvements
+
 ## v0.6.1 (August 30, 2024)
 
 ### Bug fixes

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 <https://github.com/catalystneuro/neuroconv/commit/2fbea8f05e5bd92c445fcbb6bf24de45330fcbbc>`
+   - Example: `Format Changelog Example <https://github.com/catalystneuro/neuroconv/commit/2fbea8f05e5bd92c445fcbb6bf24de45330fcbbc>`_
 
 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 <https://github.com/catalystneuro/neuroconv/commit/af91f09f300cb36ba4fee483196c8cb492c180ae>`
+   - Example: `Version Change Example <https://github.com/catalystneuro/neuroconv/commit/af91f09f300cb36ba4fee483196c8cb492c180ae>`_
 
 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 <https://github.com/catalystneuro/neuroconv/commit/89d5e41f5140c3aa1ffa066974befb21c7a01567>`
+   - Example: `Post-Release Version Bump <https://github.com/catalystneuro/neuroconv/commit/89d5e41f5140c3aa1ffa066974befb21c7a01567>`_

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 = [