Skip to content

Release 3.7.1#86

Open
snehar-nd wants to merge 7 commits into
mainfrom
release-3.7.1
Open

Release 3.7.1#86
snehar-nd wants to merge 7 commits into
mainfrom
release-3.7.1

Conversation

@snehar-nd

@snehar-nd snehar-nd commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

📋 Description

JIRA ID:

Please provide a summary of the change and the motivation behind it. Include relevant context and details.

✅ Type of Change

  • 🐞 Bug fix (non-breaking change which resolves an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 🔥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 🛠 Refactor (change that is neither a fix nor a new feature)
  • ⚙️ Config change (configuration file or build script updates)
  • 📚 Documentation (updates to docs or readme)
  • 🧪 Tests (adding new or updating existing tests)
  • 🎨 UI/UX (changes that affect the user interface)
  • 🚀 Performance (improves performance)
  • 🧹 Chore (miscellaneous changes that don't modify src or test files)

ℹ️ Additional Information

Please describe how the changes were tested, and include any relevant screenshots, logs, or other information that provides additional context.

snehar-nd and others added 5 commits June 5, 2026 13:18
@snehar-nd @claude
fix: correct EDD calculation when LMP date overflows month boundary
96bac37 
When adding 7 days to LMP caused a month overflow (e.g. Dec 25 → Jan 1),
setMonth was still using the original LMP month, producing a wrong EDD.
Now both setDate and setMonth operate on eddDate directly.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fix: amm-2339 ecd date mismatch in lmp and eod
9349532
@snehar-nd
Merge pull request #84 from PSMRI/Sn/hrp
182260b 
EOD Date was calculating wrong.
@snehar-nd
Update version from 3.6.0 to 3.7.1
3f8efea
@snehar-nd
Merge pull request #85 from PSMRI/snehar-nd-patch-3
51651b0 
Update version from 3.6.0 to 3.7.1
@coderabbitai

coderabbitai Bot commented Jun 30, 2026 •
edited
Loading

Copy link
Copy Markdown

Warning

Review limit reached

@snehar-nd, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 4 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 05a5fe3a-c247-4d1b-809b-247aeb09bd63

📥 Commits

Reviewing files that changed from the base of the PR and between e09f9df and 50d593a.

📒 Files selected for processing (2)
  • pom.xml
  • src/app/app-modules/associate-anm-mo/beneficiary-registration/ben-registration/ben-registration.component.ts

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.

@snehar-nd snehar-nd mentioned this pull request Jun 30, 2026
Merged
@snehar-nd
Merge pull request #87 from PSMRI/fix/pom-conflict-resolution
50d593a 
chore: resolve pom.xml merge conflict with main
@sonarqubecloud

sonarqubecloud Bot commented Jun 30, 2026

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@vanitha1822 vanitha1822 vanitha1822 approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@snehar-nd @vanitha1822