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 streamlines the release workflow by integrating an automatic update of the Gemfile.lock file. By running bundle install as part of the release script, it guarantees that the project's dependency lock file accurately reflects the newly released version, thereby maintaining consistency and preventing potential dependency-related issues in subsequent builds or deployments.

Highlights

• Release Script Enhancement: The dev-bin/release.sh script has been updated to include a bundle install command. This ensures that the Gemfile.lock file is automatically updated to reflect the new version of the gem after the lib/minfraud/version.rb file is modified 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 adds bundle install to the release script. This is a good change as it ensures the Gemfile.lock is updated to reflect the new version number during the release process. I have one suggestion to improve the script's robustness by adding a check to ensure the bundle command is available before it's used.

[gemini-code-assist]

For robustness, it's good practice to verify that a command exists before attempting to execute it. The script already does this for other commands like perl and rake in its pre-flight checks. A similar check should be added for bundle to ensure the script fails early with a clear error message if it's not installed.

While it would be ideal to add this check with the others at the top of the script, placing it here is a valuable improvement.

Suggested change

	# Update version in Gemfile.lock.
	bundle install
	# Update version in Gemfile.lock.
	check_command bundle
	bundle install