Release version 0.10

[moloney]

We are long overdue for a release, especially with the recent merge of multi-frame support. However there are also a number of changes to the meta data structure happening that I would like to mostly stabilize before making a release, in particular deciding if PR #96 should be merged. There is also just a lot of cruft that I would like to see taken care of.

So roughly the task list is:

• Test PR RF: Use csa_header package to parse Siemens CSA headers #96 on more real world data
• Get CI updated and functional again
• Switch from setup.py to pyproject.toml
• Look into tools to assist with cutting releases
• Update documentation to reflect recent changes, get RTD working again or switch to gh-pages

[Spenhouet]

On assisting with releases, you can automatically build and publish the package to pypi and GitHub release via github actions. I did so in this project, maybe it helps: https://github.com/Spenhouet/confluence-markdown-exporter/blob/main/.github/workflows/release.yml

I wonder if we need to block the 0.10 release by #96, or if we could just fix the build setup to get a new version. #96 could also be included in a 0.11.

[yarikoptic]

a release would indeed be appreciated!

FWIW, in a good number of projects we rely on https://intuit.github.io/ which produces release notes from github PR titles etc. E.g. see

• https://github.com/citeproc-py/citeproc-py/blob/master/.github/workflows/release.yml
• https://github.com/dandi/dandi-cli/blob/master/.github/workflows/release.yml

[Spenhouet]

@moloney Would it help you if I provide a PR which converts the project into using uv to manage dependencies and build and all the required github actions and the only thing you need to do is to add this repo as trusted publisher on pypi (see https://docs.pypi.org/trusted-publishers/adding-a-publisher/)?

After that all you would need to do to perform a release is to go onto the "actions" tab, select the new action, press "run" and then select the type of version bump (patch, minor, major). The pipeline then performs the tests, build, version bump, publishing to pypi, signing of the wheel, publishing to GitHub artifacts, performing a github release, generating release notes, tagging the branch.

[yarikoptic]

I think any release would be great to have at this point! could we create actionable plan to implement?

I would say -- please restart actions so we could fixup CI and do any of those basic RF -- could be easily done with claude code or alike.

[schoekek]

@moloney Isn't it finally time for a new release tag?