fix: update dependency io.netty:netty-transport-native-epoll to v4.2.13.final

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
io.netty:netty-transport-native-epoll (source)	4.2.12.Final → 4.2.13.Final

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Code Review

This pull request updates the version of netty-transport-native-epoll from 4.2.12.Final to 4.2.13.Final in the Java wrapper's pom.xml. Feedback was provided regarding the risk of hardcoding dependency versions, which can lead to version mismatches and runtime errors; it is recommended to let a Bill of Materials (BOM) manage these versions to ensure consistency across Netty modules.

[gemini-code-assist]

Hardcoding the version for netty-transport-native-epoll can lead to version mismatches with other Netty artifacts managed by the imported BOMs (such as grpc-bom on line 40 or google-cloud-spanner-bom on line 25). It is generally recommended to remove the explicit version and let the BOM manage it, or use a netty-bom in the dependencyManagement section to ensure all Netty modules are kept in sync. This prevents potential runtime linkage errors like NoSuchMethodError. If you must update dependencies manually outside of a BOM, verify the version's release date to ensure it is current and compatible with other libraries.

References

1. When updating dependencies, especially those not managed by a BOM, verify the version's release date to ensure it is current and compatible with other libraries.