Update brainglobe-napari-io import

[adamltyson]

Requires brainglobe/brainglobe-napari-io#61 to be merged (tests will fail until it's released), and when a new version is released, it will need to pin the latest version of brainglobe-napari-io.

[alessandrofelder]

👍
Given that the new brainglobe-napari-io is released, should we pin the version in this PR (and then merge and release)?

[willGraham01]

@alessandrofelder sorry for the dismissal I was only following your recommendation 😂

But have now pinned the new version in this update. In cases like this where we have tool updates that are dependent on releases, I think it's important we always pin new versions in the pull requests. The meta-package should handle them, but giving it some help wouldn't go amiss :L

[alessandrofelder]

I think it's important we always pin new versions in the pull requests. The meta-package should handle them ...

The metapackage (at least its user-facing part, not the future benchmarks that will depend on the dev version) will only install released versions, right. So should this technically be

I think it's important we always pin new versions before releasing?

?

[adamltyson]

Pinning (the minimum) version is always probably a good idea though right, so that pip install brainglobe -U will fetch the correct packages.

[willGraham01]

Pinning (the minimum) version is always probably a good idea though right, so that pip install brainglobe -U will fetch the correct packages.

Yeah sorry for the unhelpful comment - this is what I meant 😅 In this case, brainglobe-napari-io>=0.3.2 is now required by brainreg, so we should add that in our update to brainreg.

• The meta-package will ensure that brainglobe-napari-io and brainreg are both fetched on install.
• pip will pick up that the latest brainreg version requires brainglobe-napari-io>=0.3.2, and make sure that the latest brainreg version is installed with brainglobe-napari-io>=0.3.2.
• So, even though the meta-package currently only forces ``brainglobe-napari-io>=0.3.0`, including changes like this (one tool depends on another so update the min version) in the update PR will keep everyone happy