Bump io.netty:netty-bom from 4.2.7.Final to 4.2.8.Final

[dependabot]

Bumps io.netty:netty-bom from 4.2.7.Final to 4.2.8.Final.

Commits

• e2d9d11 [maven-release-plugin] prepare release netty-4.2.8.Final
• 2f2e437 Merge commit from fork
• d011634 Build fixes to allow using the epoll native transport on Android (#16016)
• 14fc741 Correct codec-native-quic Fragment-Host (#16015)
• caa07bb Fix Socket reading of abstract unix domain addresses (#16010)
• 640b6b7 Fix - Http3FrameCodec decode fail during unknown settings (#15998)
• 35f6ad1 Prevent ManualEventLoop to block on a racy task submission (#15937)
• 2b29b5e Use exact length when allocating the acceptedAddress byte[] (#15973) (#15984)
• b1182ed Update lz4-java version to 1.10.1 (#15978)
• debdc56 Pcap: Fix possible buffer leak when initializion fails (#15975)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

🤖 Claude Code Review

Automated Code Review - Dependency Update

Summary

This PR updates the Netty BOM (Bill of Materials) dependency from version 4.2.7.Final to 4.2.8.Final.

---

Code Quality

✅ Code follows style guide - This is a straightforward dependency version update in pom.xml:69. No code style issues.

✅ No commented-out code - No commented code present.

✅ Meaningful variable names - N/A for dependency updates.

✅ DRY principle followed - N/A for dependency updates.

✅ Defects analysis - No logic errors introduced. This is a patch version bump which typically includes bug fixes and security patches. The update appears safe as:

• It's a BOM dependency (manages versions, not direct code)
• Netty 4.2.x is a stable series
• Patch version bumps (4.2.7 → 4.2.8) are generally backwards compatible

✅ Project memory configuration - Reviewed ./.claude/CLAUDE.md. This dependency update aligns with project architecture which uses Netty through the Armeria framework. The project explicitly uses NIO transport mode (com.linecorp.armeria.transportType=nio), so Netty changes should have minimal impact.

---

Testing

⚠️ Unit tests for new functions - N/A, but recommend:

• Running the full test suite to ensure compatibility: mvn clean test
• Testing with all profiles: mvn clean install -Pcheckstyle,spotbugs,jacoco

⚠️ Integration tests - Existing integration tests should be run to verify the Netty upgrade doesn't introduce issues with:

• gRPC server startup/shutdown (AbstractGrpcTest)
• Streaming operations (export functionality)
• Connection pooling and channel management

✅ Edge cases covered - Existing tests should cover edge cases if they pass.

❓ Test coverage > 80% - Cannot verify without running tests, but this change shouldn't affect coverage.

---

Documentation

✅ Readme updated if needed - No README update needed for internal dependency bumps.

✅ API docs updated - N/A, no API changes.

✅ Inline comments - N/A for dependency updates.

⚠️ CHANGELOG.md updated - Could not locate a CHANGELOG.md file in the repository. If this project maintains a changelog, this dependency update should be documented, especially if it addresses security vulnerabilities or fixes bugs.

✅ Markdown formatting - N/A for this change.

---

Security

✅ No hardcoded credentials - No credentials involved.

✅ Input validation - N/A for dependency updates.

✅ Proper error handling - N/A for dependency updates.

✅ No sensitive data in logs - N/A for dependency updates.

✅ No license files checked in - No .lic files or AQAAAD strings in the diff.

🔍 Security consideration: Netty patch releases often include security fixes. Recommend reviewing the Netty 4.2.8.Final release notes to understand what issues were addressed: https://github.com/netty/netty/releases

---

Recommendations

1. Testing required: Run full test suite with all profiles before merging:

   mvn clean install -Pcheckstyle,spotbugs,jacoco

2. Verify shaded JAR: Ensure the shaded server JAR builds correctly:

   java -jar target/sz-sdk-grpc-server.jar --help

3. Review Netty release notes: Check what changes/fixes are in 4.2.8.Final to understand the impact.

4. Consider CHANGELOG: If the project maintains one, document this dependency update.

---

Overall Assessment

✅ APPROVED with recommendations

This is a low-risk dependency update that should be safe to merge after verification testing. The change follows best practices for dependency management and aligns with the project's architecture. No code quality, security, or architectural concerns identified.

Automated code review analyzing defects and coding standards

[senzingdevops]

Automated: approving this pull request because it includes a patch update