Release 4.6.0

[CrazyHZM]

No description provided.

[coderabbitai]

Walkthrough

The pull request updates two configuration files. The GitHub Actions release workflow is modified to reference different Maven credential secrets, changing from NEW_MAVEN_USERNAME and NEW_MAVEN_PASSWORD to MAVEN_USERNAME and MAVEN_PASSWORD without altering the deployment logic. Concurrently, the project version in pom.xml is updated from 4.6.0-SNAPSHOT to 4.6.0 in the revision property, indicating a release version bump.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to assess relatedness to the changeset.	Add a pull request description explaining the release changes, version bump, and any notable updates or breaking changes in 4.6.0.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Release 4.6.0' directly describes the main change—updating the project version to 4.6.0 and preparing for release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 074bea3 and f0a6c47.

📒 Files selected for processing (2)

• .github/workflows/release.yml (1 hunks)
• pom.xml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: build (17)
• GitHub Check: build (25-ea)
• GitHub Check: build (21)
• GitHub Check: sca

🔇 Additional comments (1)

pom.xml (1)

38-38: Version bump to release version is correct.

The revision property change from 4.6.0-SNAPSHOT to 4.6.0 is the appropriate step for transitioning to a release version. The flatten-maven-plugin configuration will properly resolve this CI-friendly version property during the build.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

❓ Verification inconclusive

Verify GitHub Secrets are configured with the new credential names.

The workflow now references MAVEN_USERNAME and MAVEN_PASSWORD secrets (lines 29–30). If these secrets are not defined in the GitHub repository, the mvn deploy step will fail with authentication errors.

Please verify:

1. That your GitHub repository has secrets named MAVEN_USERNAME and MAVEN_PASSWORD configured
2. That these secrets contain the correct credentials for OSS Sonatype Maven Central deployment
3. That the old secret names (NEW_MAVEN_USERNAME, NEW_MAVEN_PASSWORD) are no longer referenced elsewhere in CI workflows

Run the following script to search for any remaining references to the old secret names in the repository:

---

🏁 Script executed:

#!/bin/bash
# Search for references to old secret names in workflow files
rg -i "NEW_MAVEN_USERNAME|NEW_MAVEN_PASSWORD" .github/workflows/

Length of output: 0

---

Verify GitHub Secrets are configured with the new credential names.

The workflow now references MAVEN_USERNAME and MAVEN_PASSWORD secrets (lines 29–30). The script confirmed no remaining references to the old secret names (NEW_MAVEN_USERNAME, NEW_MAVEN_PASSWORD) exist in the workflows directory.

However, the workflow will fail if these secrets are not defined in your GitHub repository settings.

Please verify in your GitHub repository settings:

1. That secrets named MAVEN_USERNAME and MAVEN_PASSWORD are configured
2. That these secrets contain the correct credentials for OSS Sonatype Maven Central deployment

🤖 Prompt for AI Agents

.github/workflows/release.yml around lines 29-30: the workflow now references
secrets MAVEN_USERNAME and MAVEN_PASSWORD but will fail if they are not defined;
go to the repository Settings → Secrets and variables → Actions and ensure two
secrets named exactly MAVEN_USERNAME and MAVEN_PASSWORD exist and contain the
correct OSS Sonatype Maven Central credentials (username and password) used by
your publishing step; if your org requires different secret names, either create
these two secrets or update the workflow to match the existing secret names,
then commit the change.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.94%. Comparing base (4d66216) to head (f0a6c47).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #1395      +/-   ##
============================================
+ Coverage     82.93%   82.94%   +0.01%     
- Complexity     2973     2975       +2     
============================================
  Files           340      340              
  Lines          9833     9833              
  Branches       1178     1178              
============================================
+ Hits           8155     8156       +1     
+ Misses         1164     1163       -1     
  Partials        514      514              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.