This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
Reenable deprecation specs (and make up a plan) #6975
Closed
Closed
Commits on Feb 26, 2019
-
Teach users how to toggle deprecations off
The deprecations will lead to some "true positives" where users will use `bundle config` and remove the flag, and some "false positives" where users will be fine with the option not being remembered but still want to use the flag on a per command basis. Whatever the case, we need to tell users how to get rid of the warning once they learn and get ready for the new behavior. Otherwise it's going to get super annoying!
Configuration menu - View commit details
-
Copy full SHA for 11fecfc - Browse repository at this point
Copy the full SHA 11fecfcView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5c66f4b - Browse repository at this point
Copy the full SHA 5c66f4bView commit details -
Delay requiring --all to update everything to bundler 3
Since we haven't even yet deprecated the old behavior.
Configuration menu - View commit details
-
Copy full SHA for aaca317 - Browse repository at this point
Copy the full SHA aaca317View commit details -
Classic problems, comments do not get as curated as code, so they don't currently make sense.
Configuration menu - View commit details
-
Copy full SHA for 0e64e0d - Browse repository at this point
Copy the full SHA 0e64e0dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1d3b925 - Browse repository at this point
Copy the full SHA 1d3b925View commit details -
Remove environmental deprecations
Not necessary since no future version will run them.
Configuration menu - View commit details
-
Copy full SHA for c279801 - Browse repository at this point
Copy the full SHA c279801View commit details -
Switch gems.rb vs Gemfile warning to only warn about multiple gemfiles
It's just too early to deprecate "Gemfile", and I don't think this deprecation was even doing that.
Configuration menu - View commit details
-
Copy full SHA for afbcac5 - Browse repository at this point
Copy the full SHA afbcac5View commit details -
Actually switch the default behavior of github sources.
This fixes #6910. The idea here is that we first switch the default source to https, but not yet deprecate the custom sources, but only making them use http. On bundler 3 we can actually go and deprecate the sources.
Configuration menu - View commit details
-
Copy full SHA for 0c9592e - Browse repository at this point
Copy the full SHA 0c9592eView commit details -
Deprecate a bunch of flags in bundler 2
Under the previous code, once we stop remembering options, these flags would be automatically removed without deprecation. Instead, first deprecate the options in bundler 2, then remove them and stop remembering them in bundler 3.
Configuration menu - View commit details
-
Copy full SHA for 0b3aeeb - Browse repository at this point
Copy the full SHA 0b3aeebView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7b44d4d - Browse repository at this point
Copy the full SHA 7b44d4dView commit details
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.