From 66ab8b8673cd2282b804ab632d354b0c1c31ba31 Mon Sep 17 00:00:00 2001 From: Heberto Mayorquin Date: Fri, 30 Aug 2024 08:59:51 -0600 Subject: [PATCH] Release v0.6.1 --- CHANGELOG.md | 10 ++-------- README.md | 3 ++- docs/developer_guide/making_a_release.rst | 10 +++++----- 3 files changed, 9 insertions(+), 14 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1068f6943f..a62b16f0d5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,15 +1,9 @@ # Upcoming -### Deprecations - -### Features +## v0.6.1 (August 30, 2024) ### Bug fixes -* Fixed the JSON schema inference warning on excluded fields; also improved error message reporting of which method - triggered the error. [PR #1037](https://github.com/catalystneuro/neuroconv/pull/1037) - -### Improvements - +* Fixed the JSON schema inference warning on excluded fields; also improved error message reporting of which method triggered the error. [PR #1037](https://github.com/catalystneuro/neuroconv/pull/1037) ## v0.6.0 (August 27, 2024) diff --git a/README.md b/README.md index f90813b716..169ca8a14c 100644 --- a/README.md +++ b/README.md @@ -8,9 +8,10 @@ [![License](https://img.shields.io/pypi/l/neuroconv.svg)](https://github.com/catalystneuro/neuroconv/license.txt)

- NeuroConv logo + NeuroConv logo

Automatically convert neurophysiology data to NWB

+

Explore our documentation ยป

diff --git a/docs/developer_guide/making_a_release.rst b/docs/developer_guide/making_a_release.rst index ab6b428fb4..cb06a14d9a 100644 --- a/docs/developer_guide/making_a_release.rst +++ b/docs/developer_guide/making_a_release.rst @@ -7,23 +7,23 @@ 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: `Commit 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**: - - Ensure that no requirement files include pointers to `git`-based dependencies (including specific branches or commit hashes). All dependencies for a PyPI release should point to the released package versions that are available on conda-forge or PyPI. + - Ensure that no requirement files include pointers to `git`-based dependencies (including specific branches or commit hashes). All dependencies for a PyPI release should point to the released package versions that are available on conda-forge or PyPI. This can be done efficiently by searching for `@ git` in an IDE. 4. **Tag on GitHub**: - The title and tag should be the release version. - The changelog should be copied correspondingly. - - Check the hashes in the markdown to ensure they match with the format of previous releases. This can be done efficiently by searching for `@ git` in an IDE. + - Check the hashes in the markdown to ensure they match with the format of previous releases. 5. **Release**: @@ -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 `