Semantic release bot changes our Gemfile.lock about apollo-federation-ruby HOT 3 CLOSED

Reproduction

I spent some time investigating this and made some progress in reproducing this issue.

We have an option in semantic release rubygems that installs and update lockfiles of the appraisal to the latest version of the gem after release. That's pretty neat, it means all the specs are declared to run on the latest version.

In the config, we have an option updateGemfileLock that runs bundle exec appraisal install. Just for context, after this, the files are committed by semantic release bot using the git plugin.

This in terms generates statements like:

bundle check --gemfile='/Users/damon.aw/code/apollo-federation-ruby/gemfiles/graphql_1.10.gemfile' || bundle install --gemfile='/Users/damon.aw/code/apollo-federation-ruby/gemfiles/graphql_1.10.gemfile' --retry 1
bundle check --gemfile='/Users/damon.aw/code/apollo-federation-ruby/gemfiles/graphql_1.11.gemfile' || bundle install --gemfile='/Users/damon.aw/code/apollo-federation-ruby/gemfiles/graphql_1.11.gemfile' --retry 1
bundle check --gemfile='/Users/damon.aw/code/apollo-federation-ruby/gemfiles/graphql_1.12.gemfile' || bundle install --gemfile='/Users/damon.aw/code/apollo-federation-ruby/gemfiles/graphql_1.12.gemfile' --retry 1

Running this locally by bumping the gem version, I realized the bundle check command seems to change our Gemfile.lock in the main repo.

I've confirmed that adding --dry-run option stops the bundle check from changing the lockfiles.

Next steps

1. File an issue to Rubygems

2. We could just run bundle exec appraisal install to avoid calling bundle check for now.

from apollo-federation-ruby.

rubygems/rubygems#5325

from apollo-federation-ruby.

Closing this since I believe it was fixed at some point when the bundler version was upgraded.

from apollo-federation-ruby.