Skip to content
Merged
Changes from 1 commit
Commits
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
4 changes: 4 additions & 0 deletions dev-bin/release.sh
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ fi

check_command perl
check_command rake
check_command bundle

# Check that we're not on the main branch
current_branch=$(git branch --show-current)
Expand Down Expand Up @@ -84,6 +85,9 @@ fi

perl -pi -e "s/(?<=s.version\s{,20}=\s{,20}\').+?(?=\')/$version/g" maxmind-db.gemspec

# Update version in Gemfile.lock.
bundle install

Choose a reason for hiding this comment

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

medium

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


echo $"Test results:"

rake
Expand Down