Skip to content

Bump com.maxmind.db:maxmind-db from 3.0.0 to 4.1.0 in /modules/ingest-geoip - #590

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/gradle/modules/ingest-geoip/com.maxmind.db-maxmind-db-4.1.0
Open

Bump com.maxmind.db:maxmind-db from 3.0.0 to 4.1.0 in /modules/ingest-geoip#590
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/gradle/modules/ingest-geoip/com.maxmind.db-maxmind-db-4.1.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 29, 2026

Copy link
Copy Markdown

Bumps com.maxmind.db:maxmind-db from 3.0.0 to 4.1.0.

Release notes

Sourced from com.maxmind.db:maxmind-db's releases.

4.1.0

  • Fixed unbounded off-heap memory growth when initializing the reader in FileMode.MEMORY. The previous implementation read the database via FileChannel.read() into a heap buffer, which causes the JDK to cache temporary direct ByteBuffers in per-thread storage (sun.nio.ch.Util.BufferCache). Repeated initialization across different threads could grow this cache without bound. The reader now uses FileInputStream for MEMORY mode, which bypasses the cache. FileMode.MEMORY_MAPPED was unaffected.
  • Fixed a latent short-read bug in the multi-chunk FileMode.MEMORY load path introduced in 4.0.0. FileChannel.read(ByteBuffer) is not contractually obligated to fully fill the destination buffer; a short read could have caused silent truncation of an in-memory database. Affects databases larger than ~2GB (the default chunk size). The new chunked read loop retries until each chunk is fully populated.

4.0.2

  • Fixed a bug where enums with @MaxMindDbCreator would throw ConstructorNotFoundException when the data was stored via a pointer in the database. This commonly occurred with deduplicated data in larger databases. Reported by Fabrice Bacchella. GitHub #644 in GeoIP2-java.
  • Improved error messages when constructor invocation fails. The error now correctly identifies null values being passed to primitive parameters instead of reporting misleading boxed/primitive type mismatches.

4.0.1

  • DecodedValue is now a public class again, allowing custom NodeCache implementations to be created. The class was inadvertently made package-private in 4.0.0. Reported by Alexandros Leventakis. GitHub #321.

4.0.0

This is a major release with several breaking changes. Please see https://github.com/maxmind/MaxMind-DB-Reader-java/blob/HEAD/UPGRADING.md for detailed migration instructions.

  • Java 17 or greater is now required.
  • Added support for MaxMind DB files larger than 2GB. The library now uses an internal Buffer abstraction that can handle databases exceeding the 2GB ByteBuffer limit. Files under 2GB continue to use a single ByteBuffer for optimal performance. Requested by nonetallt. GitHub #154. Fixed by Silvano Cerza. GitHub #289.
  • Metadata.getBuildDate() has been replaced with buildTime(), which returns java.time.Instant instead of java.util.Date. The instant represents the database build time in UTC.
  • DatabaseRecord, Metadata, Network, and internal DecodedValue classes have been converted to records. The following API changes were made:
    • DatabaseRecord.getData() and DatabaseRecord.getNetwork() have been replaced with record accessor methods data() and network().
    • Simple getter methods on Metadata (e.g., getBinaryFormatMajorVersion(), getDatabaseType(), etc.) have been replaced with their corresponding record

... (truncated)

Changelog

Sourced from com.maxmind.db:maxmind-db's changelog.

4.1.0 (2026-05-12)

  • Fixed unbounded off-heap memory growth when initializing the reader in FileMode.MEMORY. The previous implementation read the database via FileChannel.read() into a heap buffer, which causes the JDK to cache temporary direct ByteBuffers in per-thread storage (sun.nio.ch.Util.BufferCache). Repeated initialization across different threads could grow this cache without bound. The reader now uses FileInputStream for MEMORY mode, which bypasses the cache. FileMode.MEMORY_MAPPED was unaffected.
  • Fixed a latent short-read bug in the multi-chunk FileMode.MEMORY load path introduced in 4.0.0. FileChannel.read(ByteBuffer) is not contractually obligated to fully fill the destination buffer; a short read could have caused silent truncation of an in-memory database. Affects databases larger than ~2GB (the default chunk size). The new chunked read loop retries until each chunk is fully populated.

4.0.2 (2025-12-08)

  • Fixed a bug where enums with @MaxMindDbCreator would throw ConstructorNotFoundException when the data was stored via a pointer in the database. This commonly occurred with deduplicated data in larger databases. Reported by Fabrice Bacchella. GitHub #644 in GeoIP2-java.
  • Improved error messages when constructor invocation fails. The error now correctly identifies null values being passed to primitive parameters instead of reporting misleading boxed/primitive type mismatches.

4.0.1 (2025-12-02)

  • DecodedValue is now a public class again, allowing custom NodeCache implementations to be created. The class was inadvertently made package-private in 4.0.0. Reported by Alexandros Leventakis. GitHub #321.

4.0.0 (2025-11-10)

This is a major release with several breaking changes. Please see https://github.com/maxmind/MaxMind-DB-Reader-java/blob/main/UPGRADING.md for detailed migration instructions.

  • Java 17 or greater is now required.
  • Added support for MaxMind DB files larger than 2GB. The library now uses an internal Buffer abstraction that can handle databases exceeding the 2GB ByteBuffer limit. Files under 2GB continue to use a single ByteBuffer for optimal performance. Requested by nonetallt. GitHub #154. Fixed by Silvano Cerza. GitHub #289.
  • Metadata.getBuildDate() has been replaced with buildTime(), which returns

... (truncated)

Commits
  • 65e28b6 Preparing for 4.1.0
  • a7e171c Set release date
  • e12266a Merge pull request #370 from maxmind/dependabot/maven/com.puppycrawl.tools-ch...
  • 74815f0 Merge pull request #368 from maxmind/greg/stf-383
  • 232dd73 Note short-read bug fix in 4.1.0 changelog
  • 2624387 Use stream channel for size lookup
  • 0ba67a3 Bump com.puppycrawl.tools:checkstyle from 13.4.1 to 13.4.2
  • d09c292 Merge pull request #369 from maxmind/dependabot/github_actions/github/codeql-...
  • cb2371e Bump github/codeql-action from 4.35.2 to 4.35.3
  • cbf83d9 Test MEMORY mode under chunkSizes matrix
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [com.maxmind.db:maxmind-db](https://github.com/maxmind/MaxMind-DB-Reader-java) from 3.0.0 to 4.1.0.
- [Release notes](https://github.com/maxmind/MaxMind-DB-Reader-java/releases)
- [Changelog](https://github.com/maxmind/MaxMind-DB-Reader-java/blob/main/CHANGELOG.md)
- [Commits](maxmind/MaxMind-DB-Reader-java@v3.0.0...v4.1.0)

---
updated-dependencies:
- dependency-name: com.maxmind.db:maxmind-db
  dependency-version: 4.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Jun 29, 2026
@dependabot @github

dependabot Bot commented on behalf of github Jun 29, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependabot. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants