Update Gemfile.lock during release

[horgh]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @horgh, I'm Gemini Code Assist¹! 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 refines the release process by integrating Gemfile.lock updates directly into the release script. This change guarantees that the dependency lock file reflects the newly released gem version, preventing potential inconsistencies and streamlining future deployments.

Highlights

• Release Script Enhancement: The release script (dev-bin/release.sh) has been updated to include a check for the bundle command, ensuring it's available before proceeding with the release.
• Gemfile.lock Update Automation: The release script now automatically runs bundle install after updating the gem version in maxmind-db.gemspec. This ensures that the Gemfile.lock file is consistently updated with the new version during the release process.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the release script to automatically update Gemfile.lock during a release. The changes are sound, adding a pre-flight check for bundle and then running bundle install to update the lockfile after the version is bumped in the gemspec. My review includes one suggestion to make the dependency update more targeted to avoid including unrelated gem updates in the release commit.

[gemini-code-assist]

Using bundle install can update all dependencies in Gemfile.lock if newer versions are available, not just the maxmind-db gem. This could unintentionally bundle unrelated dependency updates into the release commit.

To make the update more targeted, consider using bundle update maxmind-db. This will only update the maxmind-db gem and its dependencies if necessary, keeping the release commit focused on the version change.

Suggested change

	bundle install
	bundle update maxmind-db