aboutsummaryrefslogtreecommitdiffstats
path: root/lib/bundler/cli/check.rb
Commit message (Collapse)AuthorAgeFilesLines
* [Definition] Validate platform in addition to rubySamuel Giddins2016-08-251-1/+1
| | | | | # Conflicts: # lib/bundler/cli/doctor.rb
* [LockfileParser] Rename attribute to sectionSamuel Giddins2016-04-181-1/+1
|
* Generically preserve new attributes in lockfileSamuel Giddins2016-04-181-1/+1
|
* Compatibility with frozen string literalsSamuel Giddins2016-01-311-0/+1
|
* Booleanize the disable_shared_gems optionIlya Vassilevsky2016-01-211-1/+3
|
* Fix Style/SingleSpaceBeforeFirstArgErick Sasse2015-07-191-1/+1
|
* Fix Style/SpaceInsideBlockBracesAndre Arko2015-07-181-1/+1
| | | | closes #3850
* [RuboCop] Enable Style/StringLiteralsSamuel E. Giddins2015-07-151-1/+1
|
* [RuboCop] Enable Style/EmptyLinesSamuel E. Giddins2015-07-151-1/+0
|
* Merge tag 'v1.10.4'Samuel E. Giddins2015-06-161-1/+1
|\ | | | | | | Version 1.10.4
| * avoid altering BUNDLED WITH during implicit locksAndre Arko2015-06-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When either `bundle check` is run, or any application requires the `bundler/setup` file, Bundler will automatically check whether it is possible to lock the Bundle. During the lock process, Bundler updates the lock if the implicit locking changes the lock file. Starting with the 1.10 release, Bundler includes a lockfile section named BUNDLED WITH that includes the version of Bundler that generated the lockfile. In order to minimize git churn, and guarantee that the lockfile will only be changed when the user runs an explicit Bundler command, Bundler will now only add or update the BUNDLED WITH section during commands where the user asks for changes to the lock. This includes, but is not limited to, `install`, `update`, `lock`, and `package`. Running the `check` command or loading an application that uses Bundler will still now add or update the BUNDLED WITH section if, and only if, the lockfile has also changed for a different reason (such as a gem being updated). Simply using an application, by running `bundle exec` commands or by running `bin/rails` and the like, will not change the lockfile. As a result, the intended workflow with the BUNDLED WITH section is now slightly different than it was before: 1. When running `bundle install`, Bundler will update the version in the lockfile if newer than the version present. 2. Then, check in the lockfile change, exactly as you would after running install to change any other gem version. 3. Older versions of Bundler will not change the number in the lock, but will warn the user that they are out of date. refs bundler/bundler-features#80 refs #3697
* | Merge pull request #3679 from akihiro17/check-commandAndré Arko2015-06-091-1/+4
|\ \ | | | | | | Run ``` bundle check ``` with ``` disable_shared_gems ``` set to '1'
| * | Run ``` bundle check ``` with ``` disable_shared_gems ``` set to '1' if ↵akihiro172015-05-301-1/+4
| |/ | | | | | | --path option is specified
* | Print lockfile name relative from the current working directorySamuel E. Giddins2015-05-281-1/+1
| |
* | Use the actual lockfile name in messages instead of assuming its always ↵Samuel E. Giddins2015-05-281-1/+1
|/ | | | Gemfile.lock
* whitespace styleAndre Arko2014-01-261-0/+1
|
* Removed trailing whitespacesSmit Shah2014-01-081-1/+1
|
* Refactored init, check, install, update, show, outdated, cache andSmit Shah2014-01-081-0/+34
binstubs in CLI
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-15 19:21:05 +0000