[Bug]: API request fails at validation on 0.46.0, passes on 0.46.2

[cubanpit]

Code snippet

from mp_api.client import MPRester
with MPRester(api_key="<enter your api key>") as mpr:
    bandstructure = mpr.get_bandstructure_by_material_id("mp-9548")

Fails with:

ValidationError: 3 validation errors for MPDataDoc
bandstructure.setyawan_curtarolo.equivalent_labels
  Field required [type=missing, input_value={'band_gap': 0.5112999999...ap': 0.5154999999999998}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.12/v/missing
bandstructure.hinuma.equivalent_labels
  Field required [type=missing, input_value={'band_gap': 0.5112999999...ap': 0.5154999999999998}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.12/v/missing
bandstructure.latimer_munro.equivalent_labels
  Field required [type=missing, input_value={'band_gap': 0.5112999999...ap': 0.5154999999999998}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.12/v/missing

What happened?

I am attempting to get materials data from the API using mp-api 0.46.0, it only works with 0.46.2.

Version

0.46.0

Which OS?

• MacOS
• Windows
• Linux

Log output

[tsmathis]

The most reliable option is to of course use the latest version (w/ associated dependencies, etc.).

There have been upstream changes in MP's data as well as emmet-core (where all the data models live, mp-api consumes those models to make MPDataDocs).

[cubanpit]

Is there any scheduled deprecation of API? For example, a minor version (0.46.x) could support any API changes from first release date to 2 years in the future, or similar.
Otherwise, the expected behavior is to keep mp-api up to date on a weekly/monthly basis? How can product/projects which ship mp-api as part of their tools keep up with this?