Skip to content

chore: Bump BMZ dependency to 0.9.0#508

Merged
jdeschamps merged 5 commits into
mainfrom
jd/chore/bump_dps
Jul 6, 2025
Merged

chore: Bump BMZ dependency to 0.9.0#508
jdeschamps merged 5 commits into
mainfrom
jd/chore/bump_dps

Conversation

@jdeschamps
Copy link
Copy Markdown
Member

Description

Note

tldr: Depend on BMZ latest version

Background - why do we need this PR?

Currently, we fixed xarray dependency bc of the BMZ, and we depend on an old BMZ version. This allows us to depend on the latest version (0.8.0 was incompatible bc of bioimageio.specs lagging dependency on Pydantic).

Overview - what changed?

Dependency on BMZ.

Implementation - how did you implement the changes?

Update pyproject.toml and some BMZ API calls.

Changes Made

Modified features or files

  • pyproject.toml
  • model_description.py

How has this been tested?

CI and local.

Related Issues

#495 (comment)

Thanks @mese79 !!!


Please ensure your PR meets the following requirements:

  • Code builds and passes tests locally, including doctests
  • New tests have been added (for bug fixes/features)
  • Pre-commit passes
  • PR to the documentation exists (for bug fixes / features)

@jdeschamps jdeschamps merged commit 9a1723f into main Jul 6, 2025
12 of 13 checks passed
@jdeschamps jdeschamps deleted the jd/chore/bump_dps branch July 6, 2025 21:00
tmuird pushed a commit to tmuird/careamics that referenced this pull request Jan 3, 2026
## Description

<!-- This section provides the necessary background and information for
reviewers to
understand the code and have the correct mindset when examining changes.
-->

> [!NOTE]  
> **tldr**: Depend on BMZ latest version

### Background - why do we need this PR?

<!-- What problem are you solving? Describe in a few sentences the state
before
this PR. Use code examples if useful. -->

Currently, we fixed `xarray` dependency bc of the BMZ, and we depend on
an old BMZ version. This allows us to depend on the latest version
(`0.8.0` was incompatible bc of bioimageio.specs lagging dependency on
Pydantic).

### Overview - what changed?

<!-- What aspects and mechanisms of the code base changed? Describe only
the general
idea and overarching features. -->

Dependency on BMZ.

### Implementation - how did you implement the changes?

<!-- How did you solve the issue technically? Explain why you chose this
approach and
provide code examples if applicable (e.g. change in the API for users).
-->

Update `pyproject.toml` and some BMZ API calls.

## Changes Made

<!-- This section highlights the important features and files that
reviewers should
pay attention to when reviewing. Only list important features or files,
this is useful for
reviewers to correctly assess how deeply the modifications impact the
code base.

For instance:

### New features or files
- `NewClass` added to `new_file.py`
- `new_function` added to `existing_file.py`

...
-->


### Modified features or files

<!-- List important modified features or files. -->
- `pyproject.toml`
- `model_description.py`


## How has this been tested?

<!-- Describe the tests that you ran to verify your changes. This can be
a short
description of the tests added to the PR or code snippet to reproduce
the change
in behaviour. -->

CI and local.

## Related Issues

<!-- Link to any related issues or discussions. Use keywords like
"Fixes", "Resolves",
or "Closes" to link to issues automatically. -->


CAREamics#495 (comment)


Thanks @mese79 !!!

---

**Please ensure your PR meets the following requirements:**

- [x] Code builds and passes tests locally, including doctests
- [ ] New tests have been added (for bug fixes/features)
- [x] Pre-commit passes
- [ ] PR to the documentation exists (for bug fixes / features)

---------

Co-authored-by: Mehdi Seifi <mehdiseifi@gmail.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
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.

3 participants