`Bundler.with_original_env` vs `Bundler.with_unbundled_env`

[ngan]

I believe this change has broken things for us for environments that use bundler environment variables:
https://github.com/rails/spring/pull/661/files#diff-badda36a241454b100b8aba52c978271cff008a57451d78e600fa62c3d65d8d9L96-R96

For example, if you set the BUNDLE_PATH=some/path/to/bundle environment variable, it's not picked up because of the Bundler.with_unbundled_env change.

[ngan]

@rafaelfranca I couldn't find the reason in the PR for the change. Can you help clarify? Thank you!

[ngelx]

Same here. Downgrading to 3.1.1 fix the issue.

[rafaelfranca]

Fixed in 7fcb742

[gee-forr]

Is there any chance we could get this change released as a patch-level release on 4.0? We've been unable to upgrade to spring 4.0 because our gems locations are non standard.

Much ❤️ - thanks for the gem. It saves us ridiculous amounts of time when devving on some of our larger systems

[gee-forr]

Just a smol bump to ping @rafaelfranca if it's possible to release a 4.0.1 that includes this fix?

[heberuriegas]

+1 with the 4.0.1 release