prepare v0.4.0 release

[leifdenby]

Describe your changes

Update changelog and pyproject.toml for v0.4.0 release

No change of dependencies

Issue Link

n/a

Type of change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📖 Documentation (Addition or improvements to documentation)

Checklist before requesting a review

• My branch is up-to-date with the target branch - if not update your fork with the changes from the target branch (use pull with --rebase option if possible).
• I have performed a self-review of my code
• For any new/modified functions/classes I have added docstrings that clearly describe its purpose, expected inputs and returned values
• I have placed in-line comments to clarify the intent of any hard-to-understand passages of my code
• I have updated the documentation to cover introduced code changes
• I have added tests that prove my fix is effective or that my feature works
• I have given the PR a name that clearly describes the change, written in imperative form (context).
• I have requested a reviewer and an assignee (assignee is responsible for merging)

Checklist for reviewers

Each PR comes with its own improvements and flaws. The reviewer should check the following:

• the code is readable
• the code is well tested
• the code is documented (including return types and parameters)
• the code is easy to maintain

Author checklist after completed review

• I have added a line to the CHANGELOG describing this change, in a section
  reflecting type of change (add section where missing):
  • added: when you have added new functionality
  • changed: when default behaviour of the code has been changed
  • fixes: when your contribution fixes a bug

Checklist for assignee

• PR is up to date with the base branch
• the tests pass
• author has added an entry to the changelog (and designated the change as added, changed or fixed)
• Once the PR is ready to be merged, squash commits and merge the PR.

[prajwal-tech07]

Thanks @leifdenby! Took a careful look — the version bump is complete and correct: pyproject.toml is the only version source (__version__ from #56 reads package metadata at runtime, so nothing else needs bumping), all 9 PRs merged since v0.3.0 are covered in the changelog (#46, #56, #59, #65, #81, #117, #123, #140, #146), and the module paths in the release summary all check out (save.neural_lam.torch_tensors, wmg.diagnostics.check_graph_consistency).

One small thing worth fixing before tagging, since release notes freeze once published: the #65 entry (README test isolation, @Shristi-Goel) sits under v0.3.0 → ### Maintenance, but it was merged in March 2026 — four months after v0.3.0 was tagged — so it actually ships with v0.4.0. I'd move it to the new v0.4.0 → ### Maintenance section. Its link also points at /pull/64 while the text says #65 — should be https://github.com/mllam/weather-model-graphs/pull/65.

Very minor (take it or leave it): the check_graph_consistency entry references (#42) as plain text — could be [\#59](https://github.com/mllam/weather-model-graphs/pull/59), @AdMub to match the link + credit style of the other entries.

Approving — excited to see v0.4.0 go out! 🎉 I'll bump neural-lam #596 to weather-model-graphs==0.4.0 as soon as it's released.

[prajwal-tech07]

Thanks @leifdenby! Took a careful look - the version bump is complete and correct: pyproject.toml is the only version source (__version__ from #56 reads package metadata at runtime, so nothing else needs bumping), all 9 PRs merged since v0.3.0 are covered in the changelog (#46, #56, #59, #65, #81, #117, #123, #140, #146), and the module paths in the release summary all check out (save.neural_lam.torch_tensors, wmg.diagnostics.check_graph_consistency).

One small thing worth fixing before tagging, since release notes freeze once published: the #65 entry (README test isolation, @Shristi-Goel) sits under v0.3.0 → ### Maintenance, but it was merged in March 2026 - four months after v0.3.0 was tagged - so it actually ships with v0.4.0. Could you move it over to the new v0.4.0 → ### Maintenance section. Its link also points at /pull/64 while the text says #65 - should be https://github.com/mllam/weather-model-graphs/pull/65.

Very minor : the check_graph_consistency entry references (#42) as plain text - could be [\#59](https://github.com/mllam/weather-model-graphs/pull/59), @AdMub to match the link + credit style of the other entries.

Excited to see v0.4.0 go out! 🎉 I'll bump neural-lam #596 to weather-model-graphs==0.4.0 as soon as it's released.