Skip to content

Release 4.1.0#371

Merged
horgh merged 3 commits into
mainfrom
greg/stf-411-release
May 12, 2026
Merged

Release 4.1.0#371
horgh merged 3 commits into
mainfrom
greg/stf-411-release

Conversation

@oschwald
Copy link
Copy Markdown
Member

  • Set release date
  • Preparing for 4.1.0

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the project version to 4.1.0 and refreshes the copyright dates across the documentation and build files. Feedback suggests updating the Gradle documentation to use the modern implementation configuration instead of the deprecated compile keyword. Additionally, it is recommended to keep the japicmp.baselineVersion at the previous stable version (4.0.2) to ensure API compatibility checks remain effective during the release process.

Comment thread README.md Outdated
}
dependencies {
compile 'com.maxmind.db:maxmind-db:4.0.2'
compile 'com.maxmind.db:maxmind-db:4.1.0'
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The compile configuration in Gradle has been deprecated for a long time and was removed in Gradle 7.0. It is recommended to use implementation instead for library dependencies in documentation examples to ensure they work with modern Gradle versions.

Suggested change
compile 'com.maxmind.db:maxmind-db:4.1.0'
implementation 'com.maxmind.db:maxmind-db:4.1.0'

Comment thread pom.xml
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<!-- Baseline version for API compatibility checking. Update after each release. -->
<japicmp.baselineVersion>4.0.2</japicmp.baselineVersion>
<japicmp.baselineVersion>4.1.0</japicmp.baselineVersion>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

Updating the japicmp.baselineVersion to the current version (4.1.0) during the release process effectively disables the API compatibility check for this release. The plugin will attempt to compare the current build against version 4.1.0, which likely hasn't been published yet (causing a build failure) or will result in a trivial comparison against itself. It is best practice to keep the baseline at the previous stable version (4.0.2) until the release is finalized, and only update it for the subsequent development cycle.

Suggested change
<japicmp.baselineVersion>4.1.0</japicmp.baselineVersion>
<japicmp.baselineVersion>4.0.2</japicmp.baselineVersion>

@horgh horgh merged commit 4db71a3 into main May 12, 2026
27 checks passed
@horgh horgh deleted the greg/stf-411-release branch May 12, 2026 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants