Skip to content

Add changelog entry for #231#235

Merged
oschwald merged 3 commits intomainfrom
wstorey/windows-extension-name
Feb 9, 2026
Merged

Add changelog entry for #231#235
oschwald merged 3 commits intomainfrom
wstorey/windows-extension-name

Conversation

@horgh
Copy link
Contributor

@horgh horgh commented Feb 9, 2026

No description provided.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@gemini-code-assist
Copy link

Summary of Changes

Hello @horgh, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily updates the project's changelog to reflect a recent fix for Windows build configurations. It addresses an issue where the build process was looking for an outdated library name, ensuring compatibility with newer versions of libmaxminddb by correcting a warning message.

Highlights

  • Changelog Update: A new entry for version 1.13.2 has been added to CHANGELOG.md, documenting a fix for Windows build configurations related to the libmaxminddb library.
  • Windows Build Configuration Fix: The ext/config.w32 file has been updated to correctly reference maxminddb.lib instead of libmaxminddb.lib in a warning message, aligning with changes in libmaxminddb version 1.6.0 where the lib prefix was removed.
Changelog
  • CHANGELOG.md
    • Added a new entry for version 1.13.2 detailing the update to the Windows build configuration to use the correct libmaxminddb name (maxminddb.lib).
  • ext/config.w32
    • Modified a warning message to correctly reference maxminddb.lib instead of libmaxminddb.lib when the library is not found during the build process.
Activity
  • No human activity (comments, reviews, etc.) has been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy link

@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

The pull request updates the Windows build configuration warning to correctly reflect the library name and adds a corresponding entry to the changelog for version 1.13.2. The changes are correct and improve the accuracy of the build feedback. However, the changelog entry is missing the release date, which is standard for this project. Additionally, please ensure that the version number in ext/php_maxminddb.h is updated to 1.13.2 to match the changelog, as it currently remains at 1.13.1.

CHANGELOG.md Outdated
CHANGELOG
=========

1.13.2

Choose a reason for hiding this comment

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

medium

The changelog entry for version 1.13.2 is missing the release date, which is present in all previous entries. Adding a placeholder or the actual date will maintain consistency and ensure the header length matches the existing 19-dash underline.

Suggested change
1.13.2
1.13.2 (YYYY-MM-DD)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, but we don't see dates until we actually release. This is just adding to the changelog with things that aren't released yet.

CHANGELOG.md Outdated
CHANGELOG
=========

1.13.2
Copy link
Member

Choose a reason for hiding this comment

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

We probably should make this at least a minor version bump given that it would likely require build changes for some consumers.

@oschwald oschwald merged commit 5755a1d into main Feb 9, 2026
83 checks passed
@oschwald oschwald deleted the wstorey/windows-extension-name branch February 9, 2026 21:13
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