Skip to content

Conversation

@ericspod
Copy link
Member

Description

This adds the "what's new" page for the minor 1.5.2 release. This commit should probably just be cherry-picked for the release. Branch rules will have to be temporarily broken to allow the PR past blossom as well, since no code is modified here this is safe and it's only the documentation generation that should be checked.

Types of changes

  • Non-breaking change (fix or new feature that would not break existing functionality).
  • Breaking change (fix or new feature that would cause existing functionality to change).
  • New tests added to cover the changes.
  • Integration tests passed locally by running ./runtests.sh -f -u --net --coverage.
  • Quick tests passed locally by running ./runtests.sh --quick --unittests --disttests.
  • In-line docstrings updated.
  • Documentation updated, tested make html command in the docs/ folder.

Signed-off-by: Eric Kerfoot <17726042+ericspod@users.noreply.github.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 25, 2026

📝 Walkthrough

Walkthrough

Adds release notes documentation for version 1.5.2 by creating docs/source/whatsnew_1_5_2.md and updating docs/source/whatsnew.rst to include it in the toctree. Also removes emoji from the header in docs/source/whatsnew_1_5_1.md. The 1.5.2 notes reference a security advisory (GHSA-9rg3-9pvr-6p27). No public API or code behavior changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed Title accurately reflects the main change: adding release notes for version 1.5.2.
Description check ✅ Passed Description covers the main purpose, identifies documentation updates as checked, and notes testing was performed.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@docs/source/whatsnew_1_5_1.md`:
- Line 2: The release-note headers are inconsistent: the header in
whatsnew_1_5_1.md is plain "# What's new in 1.5.1" but whatsnew_1_5_2.md still
includes emojis; to fix, edit whatsnew_1_5_2.md and remove the emoji from its
top header so it matches the plain format (change its header to "# What's new in
1.5.2"), ensuring the rest of the file follows the same non-emoji style as the
"# What's new in 1.5.1" header.

In `@docs/source/whatsnew_1_5_2.md`:
- Line 6: Fix the grammar and potential duplication in the release note sentence
in docs/source/whatsnew_1_5_2.md that currently reads "With the upgrade support
for PyTorch 2.8, MONAI now directly support NVIDIA GeForce RTX 50 series GPUs
and other Blackwell-based GPUs!": change "support" to "supports" and then either
remove the sentence if the same claim already exists in the 1.5.1 notes, or
update it to explain what specifically changed in 1.5.2 (e.g., bugfixes,
improved compatibility, or expanded GPU support) so the note is not a duplicate.

Signed-off-by: Eric Kerfoot <17726042+ericspod@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.

1 participant