Open zeissmicroscopy opened 1 month ago
BREAKING CHANGE: Either remove this line or add a short description describing the nature of the breaking change. Be aware that this will [trigger a MAJOR update pushed to PyPI when merged to main].
---ADAPT ME--- [ ] I followed the How to structure your PR. [ ] Based on Commit Parsing: In case a new major release will be created (because the body or footer begins with 'BREAKING CHANGE:'), I created a new Jupyter notebook with a matching version. [ ] Based on Commit Parsing: In case a new minor/patch release will be created (because PR title begins with 'feat'/('fix' or 'perf')), I optionally created a new Jupyter notebook with a matching version. [ ] In case of API changes, I updated API.md.
Summary of the change(s) and which issue(s) is/are fixed Relevant motivation and context Dependencies required for this change
Fixes # (issue) ---ADAPT ME---
BREAKING CHANGE: Either remove this line or add a short description describing the nature of the breaking change. Be aware that this will [trigger a MAJOR update pushed to PyPI when merged to main].
---ADAPT ME---
[ ] I followed the How to structure your PR.
[ ] Based on Commit Parsing: In case a new major release will be created (because the body or footer begins with 'BREAKING CHANGE:'), I created a new Jupyter notebook with a matching version.
[ ] Based on Commit Parsing: In case a new minor/patch release will be created (because PR title begins with 'feat'/('fix' or 'perf')), I optionally created a new Jupyter notebook with a matching version.
[ ] In case of API changes, I updated API.md.
Summary of the change(s) and which issue(s) is/are fixed
Relevant motivation and context
Dependencies required for this change
Fixes # (issue)
---ADAPT ME---