[Bug]: Latest version of Xarray (v0.11.0) introduces breaking change that affects many xCDAT APIs

[tomvothecoder]

What happened?

Related to https://github.com/E3SM-Project/e3sm_diags/issues/1019

Xarray 2025.11.0 was released two days ago. Here's the changelog.

There is a breaking change here related to Xarray preserving attributes by default for all operations, which I don't think we want/need. This change breaks many xCDAT operations (many unit tests fails here).

What did you expect to happen? Are there are possible answers you came across?

No response

Minimal Complete Verifiable Example (MVCE)

Relevant log output

Anything else we need to know?

No response

Environment

Latest xarray=2025.11.0 with latest xcdat

[tomvothecoder]

Hey @jasonb5 I am heading out for vacation until 11/28.

This is a critical item that needs to be taken care of. Can you temporarily constrain xarray<2025.11.0 in:

1. conda env yml files
2. pyproject.toml
3. conda-forge feedstock v0.10.1 with a patch.

Thank you!

[jasonb5]

Leaving this open so we can address removing the pin in the future.