Skip to content

Release 5.1.0 #699

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
horgh merged 4 commits into from
May 12, 2026
+10 −7
Merged

Release 5.1.0 #699

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
47c6e6f
Update maxmind-db to 4.1.0
oschwald May 12, 2026
0b925c1
Update lock file
oschwald May 12, 2026
08024f9
Set release date
oschwald May 12, 2026
d6ab648
Preparing for 5.1.0
oschwald May 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,12 @@
CHANGELOG
=========

5.1.0 (unreleased)
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
Expand Down
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ To do this, add the dependency to your pom.xml:
<dependency>
<groupId>com.maxmind.geoip2</groupId>
<artifactId>geoip2</artifactId>
<version>5.0.2</version>
<version>5.1.0</version>
</dependency>
```

Expand All @@ -30,7 +30,7 @@ repositories {
mavenCentral()
}
dependencies {
implementation 'com.maxmind.geoip2:geoip2:5.0.2'
implementation 'com.maxmind.geoip2:geoip2:5.1.0'
}
```

Expand Down
2 changes: 1 addition & 1 deletion mise.lock
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# @generated - this file is auto-generated by `mise lock` https://mise.jdx.dev/dev-tools/mise-lock.html

[[tools.java]]
version = "26.0.0"
version = "26.0.1"
backend = "core:java"

[[tools.maven]]
Expand Down
6 changes: 3 additions & 3 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
<modelVersion>4.0.0</modelVersion>
<groupId>com.maxmind.geoip2</groupId>
<artifactId>geoip2</artifactId>
<version>5.0.2</version>
<version>5.1.0</version>
<packaging>jar</packaging>
<name>MaxMind GeoIP2 API</name>
<description>GeoIP2 webservice client and database reader</description>
Expand Down Expand Up @@ -53,7 +53,7 @@
<dependency>
<groupId>com.maxmind.db</groupId>
<artifactId>maxmind-db</artifactId>
<version>4.0.2</version>
<version>4.1.0</version>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
Expand Down Expand Up @@ -103,7 +103,7 @@
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<!-- Baseline version for API compatibility checking. Update after each release. -->
<japicmp.baselineVersion>5.0.2</japicmp.baselineVersion>
<japicmp.baselineVersion>5.1.0</japicmp.baselineVersion>
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot May 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Updating japicmp.baselineVersion to 5.1.0 is premature. This property is used by the maven-antrun-plugin (line 320) to download the baseline JAR from Maven Central for API compatibility checks. Since version 5.1.0 is the version currently being released and is not yet available in Maven Central, the build will fail with a 404 error when the api-compat profile is active. As noted in the comment on line 105, this should be updated after the release is published. For now, it should continue to point to the previous release (5.0.2).

Suggested change
<japicmp.baselineVersion>5.1.0</japicmp.baselineVersion>
<japicmp.baselineVersion>5.0.2</japicmp.baselineVersion>

</properties>
<build>
<plugins>
Expand Down
Loading