Skip to content

Conversation

@jcupitt
Copy link
Collaborator

@jcupitt jcupitt commented Feb 25, 2025

see #98

@bgilbert
Copy link
Collaborator

Is the plan to skip the 1.2.0 release and go directly to 1.2.1, then?

@xz0x
Copy link

xz0x commented Mar 4, 2025

Thanks for the PR! I noticed the Issue is closed—should I follow up in the PR instead? I’d love to test the fix with my PoC and provide feedback. Let me know how you’d like to proceed!

@jcupitt
Copy link
Collaborator Author

jcupitt commented Mar 28, 2025

Sorry for the silence, I've been trapped for weeks on another project :( I'm going to DICOM for the next week or two and catch up again.

@bgilbert I think I'll aim for a formal 1.3 release with this fix plus the scrap of new API for catenation support.

@xz0x if you could test this branch that'd be great, thanks!

@jcupitt
Copy link
Collaborator Author

jcupitt commented Mar 28, 2025

Hmm, wait, now I reread the CHANGELOG let's do 1.2.0 instead as you suggested. I'll update this PR.

@jcupitt jcupitt force-pushed the fix-aithmetic-exception branch from e77b3ac to 34d0614 Compare March 28, 2025 09:31
@jcupitt jcupitt merged commit 2efb7f3 into main Apr 9, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants