-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Removed compatibility hack for old rubies. #6315
Conversation
I wonder why we still test with Ruby 1.8 |
I think @segiddins left it there to make backporting to 1.x branches easier for the time being. Not sure though. |
Yes, it is to make it possible to be confident back porting to 1.x will not break things |
Since the 1.x series has been branched off of master for a while now, I think it makes sense to stop testing master against old rubies, and make that compatibility part of the backport work if/when backports are made. 👍 |
At the very least, I'd like to keep them until 2.0 final is released (and we dont even have a prerelease out yet). Since we still need to support 1.16.x as the latest stable version |
This is no rush. I wait a release day of 2.0. |
I don't really see the point of keeping 1.8 compatibility on master... I can see backports needing a bit of extra work if it's dropped but the alternative is "extra work by default". |
☔ The latest upstream changes (presumably #6657) made this pull request unmergeable. Please resolve the merge conflicts. |
Rebased. I will merge this to master branch after creating 2-0-0-stable branch. |
@bundlerbot r+ |
6315: Removed compatibility hack for old rubies. r=hsbt a=hsbt ### What was the end-user problem that led to this PR? Nothing. ### What is your fix for the problem, implemented in this PR? Bundler will never use them in version 2. Co-authored-by: SHIBATA Hiroshi <[email protected]>
Build succeeded |
6315: Removed compatibility hack for old rubies. r=hsbt a=hsbt Nothing. Bundler will never use them in version 2. Co-authored-by: SHIBATA Hiroshi <[email protected]> (cherry picked from commit 1b2559a)
## 2.0.2 (2019-05-13) Changes: - Fixes for Bundler integration with ruby-src ([#6941](rubygems/bundler#6941), [#6973](rubygems/bundler#6973), [#6977](rubygems/bundler#6977), [#6315](rubygems/bundler#6315), [#7061](rubygems/bundler#7061)) - Use `__dir__` instead of `__FILE__` when generating a gem with `bundle gem` ([#6503](rubygems/bundler#6503)) - Use `https` on externals links in the Bundler gemspec ([#6721](rubygems/bundler#6721)) - Removed duplicate gem names from the suggested `did you mean` list for gem typos ([#6739](rubygems/bundler#6739)) - Removed Ruby 1.x compatibility code ([#6764](rubygems/bundler#6764), [#6806](rubygems/bundler#6806)) - Fixed an issue where `bundle remove` would crash with certain Gemfiles ([#6768](rubygems/bundler#6769)) - Fixed indentation in the Bundler executable template ([#6773](rubygems/bundler#6773)) - Fixed an issue where plugins could register for the same Bundler hook multiple times ([#6775](rubygems/bundler#6775)) - Changed the "multiple sources" message in `bundle install` to be a warning instead of an error ([#6790](rubygems/bundler#6790)) - Fixed a bug where path gems would break when using `only_update_to_newer_versions` ([#6774](rubygems/bundler#6774)) - Fixed a bug where installing plugins with the `--delpoyment` setting would fail ([#6805](rubygems/bundler#6805)) - Fixed an issue where `bundle update` couldn't update & install a gem when `no_install` was set (a `bundle package` config) ([#7078](rubygems/bundler#7078)) - Fixed an issue where users could not run `bundle exec` on default gems ([#6963](rubygems/bundler#6963)) - Updated vendor libraries to their latest version ([#7076](rubygems/bundler#7067), [#7068](rubygems/bundler#7068)) - Fixed an issue where the `github` source was not using `https` by default that we mentioned in the 2.0 release ([#7182](rubygems/bundler#7182)) - Fixed an issue where `rake release` was not outputting the message to users asking for a 2fa token ([#7199](rubygems/bundler#7199)) Documentation: - Fix incorrect documented `BUNDLE_PATH_RELATIVE_TO_CWD` env var ([#6751](rubygems/bundler#6751)) - Update URLs in Bundler's documentation to use `https` ([#6935](rubygems/bundler#6935)) ## 2.0.1 (2019-01-04) Changes: - Relaxed RubyGems requirement to `>= 2.5.0` ([#6867](rubygems/bundler#6867)) ## 2.0.0 (2019-01-03) No new changes ## 2.0.0.pre.3 (2018-12-30) Breaking Changes: - Bundler 2 now requires RubyGems 3.0.0 at minimum Changes: - Ruby 2.6 compatibility fixes (@segiddins) - Import changes from Bundler 1.17.3 release Note: To upgrade your Gemfile to Bundler 2 you will need to run `bundle update --bundler` ## 2.0.0.pre.2 (2018-11-27) Breaking Changes: - `:github` source in the Gemfile now defaults to using HTTPS Changes - Add compatibility for Bundler merge into ruby-src Note: To upgrade your Gemfile to Bundler 2 you will need to run `bundle update --bundler` ## 2.0.0.pre.1 (2018-11-09) Breaking Changes: - Dropped support for versions of Ruby < 2.3 - Dropped support for version of RubyGems < 2.5 - Moved error messages from STDOUT to STDERR Note: To upgrade your Gemfile to Bundler 2 you will need to run `bundle update --bundler`
What was the end-user problem that led to this PR?
Nothing.
What is your fix for the problem, implemented in this PR?
Bundler will never use them in version 2.