Closed andyw8 closed 8 months ago
If we check out the second-newest commit on main, 614084b54bc7b4bbaef8743b5620055d1fa9c3a5, bundle
runs fine without changing to Gemfile.lock
. So f529cdcab2a8c4e585ffe1a4e24fe850b260db4c is to blame.
~The problem seems to begin with rbi
0.1.8, it's fine with 0.1.7.~
There must be a bug in Bundler, try this on main
:
gem "rbi"
to Gemfile (probably any gem would work)bundle
git diff
and observe that the PLATFORMS
haven't changedbundle
againgit diff
and observe this time the PLATFORMS
have changedOpened an issue on bundler: https://github.com/rubygems/rubygems/issues/7536
https://github.com/Shopify/spoom/pull/528 got auto-closed because https://github.com/Shopify/spoom/pull/534 was opened, and it seems to no longer have the PLATFORMS
problem. 🤔
I'll close this since it seems to have resolved itself.
Should I close the bundler issue since this is no longer reproducible?
Yeah, let's close and we can re-open if it happens again.
Running
bundle
locally on main is causing changes toGemfile.lock
: