chore(deps-dev): bump com.maxmind.geoip2:geoip2 from 4.3.0 to 5.1.0

[dependabot]

Bumps com.maxmind.geoip2:geoip2 from 4.3.0 to 5.1.0.

Release notes

Sourced from com.maxmind.geoip2:geoip2's releases.

5.1.0

• Updated maxmind-db dependency to 4.1.0. This release fixes an issue with unbounded off-heap memory growth when using FileMode.MEMORY and a latent short-read bug when loading databases larger than 2GB into memory.
• Added WebServiceClient.Builder.maxRetries(int) to bound transport-failure retries (default 1; set 0 to disable). See the README for retry semantics. Behavior change: previously, transient transport failures (connection reset, broken pipe, etc.) surfaced to callers immediately. They are now retried once by default; pass .maxRetries(0) to restore the prior behavior.

5.0.2

• Fixed an issue where decoding IpRiskResponse from the IP Risk database would fail when the ip_risk field was not present in the database record. The ipRisk field now defaults to 0.0 when not present. A value of 0.0 indicates that the risk score was not set in the database. In a future major release, this field may be changed to a nullable Double to better distinguish between "no data" and "zero risk". Reported by Fabrice Bacchella. GitHub #644.
• Updated maxmind-db dependency to 4.0.2. This fixes a bug where enums with @MaxMindDbCreator would throw ConstructorNotFoundException when the data was stored via a pointer in the database, commonly occurring with deduplicated data in larger databases. It also improves error messages when constructor invocation fails. Reported by Fabrice Bacchella. GitHub #644.

5.0.1

• Updated maxmind-db dependency to 4.0.1. This makes DecodedValue public again, allowing custom NodeCache implementations to be created. GitHub #636.

5.0.0

• BREAKING: All model and record classes have been converted to Java records. This provides a more modern, immutable data model with automatic implementations of equals(), hashCode(), and toString(). The abstract classes AbstractRecord, AbstractNamedRecord, AbstractResponse, AbstractCountryResponse, AbstractCityResponse, and IpBaseResponse have been removed. Record components can be accessed using the new accessor methods (e.g., city(), country(), location()). The traditional getter methods (e.g., getCity(), getCountry(), getLocation()) are still available but have been deprecated and will be removed in version 6.0.0.
• BREAKING: RepresentedCountry is now a separate record type instead of extending Country. It shares the same fields as Country but adds a type field.
• The deprecation notices for IP Risk database support have been removed. IP Risk database support will continue to be maintained.
• A new Anonymizer record has been added to the InsightsResponse model. This record consolidates anonymizer information including VPN confidence scores, network last seen dates, and provider names. It includes the following fields: confidence, isAnonymous, isAnonymousVpn, isHostingProvider, isPublicProxy, isResidentialProxy, isTorExitNode, networkLastSeen, and providerName.

... (truncated)

Changelog

Sourced from com.maxmind.geoip2:geoip2's changelog.

5.1.0 (2026-05-12)

• Updated maxmind-db dependency to 4.1.0. This release fixes an issue with unbounded off-heap memory growth when using FileMode.MEMORY and a latent short-read bug when loading databases larger than 2GB into memory.
• Added WebServiceClient.Builder.maxRetries(int) to bound transport-failure retries (default 1; set 0 to disable). See the README for retry semantics. Behavior change: previously, transient transport failures (connection reset, broken pipe, etc.) surfaced to callers immediately. They are now retried once by default; pass .maxRetries(0) to restore the prior behavior.

5.0.2 (2025-12-08)

• Fixed an issue where decoding IpRiskResponse from the IP Risk database would fail when the ip_risk field was not present in the database record. The ipRisk field now defaults to 0.0 when not present. A value of 0.0 indicates that the risk score was not set in the database. In a future major release, this field may be changed to a nullable Double to better distinguish between "no data" and "zero risk". Reported by Fabrice Bacchella. GitHub #644.
• Updated maxmind-db dependency to 4.0.2. This fixes a bug where enums with @MaxMindDbCreator would throw ConstructorNotFoundException when the data was stored via a pointer in the database, commonly occurring with deduplicated data in larger databases. It also improves error messages when constructor invocation fails. Reported by Fabrice Bacchella. GitHub #644.

5.0.1 (2025-12-02)

• Updated maxmind-db dependency to 4.0.1. This makes DecodedValue public again, allowing custom NodeCache implementations to be created. GitHub #636.

5.0.0 (2025-11-20)

• BREAKING: All model and record classes have been converted to Java records. This provides a more modern, immutable data model with automatic implementations of equals(), hashCode(), and toString(). The abstract classes AbstractRecord, AbstractNamedRecord, AbstractResponse, AbstractCountryResponse, AbstractCityResponse, and IpBaseResponse have been removed. Record components can be accessed using the new accessor methods (e.g., city(), country(), location()). The traditional getter methods (e.g., getCity(), getCountry(), getLocation()) are still available but have been deprecated and will be removed in version 6.0.0.
• BREAKING: RepresentedCountry is now a separate record type instead of extending Country. It shares the same fields as Country but adds a type field.

... (truncated)

Commits

• d6ab648 Preparing for 5.1.0
• 08024f9 Set release date
• 0b925c1 Update lock file
• 47c6e6f Update maxmind-db to 4.1.0
• b232d27 Merge pull request #698 from maxmind/dependabot/maven/com.jcabi-jcabi-matcher...
• a8950f3 Merge pull request #697 from maxmind/dependabot/maven/com.puppycrawl.tools-ch...
• 6217e30 Bump com.jcabi:jcabi-matchers from 1.8.0 to 1.9.0
• a92ca45 Bump com.puppycrawl.tools:checkstyle from 13.4.1 to 13.4.2
• 77defec Merge pull request #693 from maxmind/greg/stf-322
• 716c849 STF-322: Bump CHANGELOG version to 5.1.0 per review
• 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 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)