Make a new release

[surchs]

We have gone for a pretty long time since the last release. The plan is to change that: neurobagel/planning#64. But first we need a release of our current app.

• draft a release with basic notes
• make it a patch version release 🤷

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[surchs]

It's been a little while since the last release... And before the big work starts, it would make sense to release the current state of the app

[surchs]

Drafted release is here. I'll move issue to tracked until after we have addressed #835

[rmanaem]

@surchs I suggest going with a minor release as opposed to a patch.

[surchs]

@rmanaem the release draft is here: https://github.com/neurobagel/annotation_tool/releases the proposal is to go v0.2.0 to v0.3.0

[surchs]

Release will go in once

• [FIX] Addressed the issue with missing mutations #837

is merged