aboutsummaryrefslogtreecommitdiffstats
path: root/lib/bundler/cli/outdated.rb
Commit message (Collapse)AuthorAgeFilesLines
* Improve and fixed guide style code.Guillermo Guerrero2016-11-151-43/+91
|
* Refactoring of @lucasmazza fix w/ specs.chrismo2016-11-151-4/+4
| | | | | | | | | The only existing spec coverage was essentially integration level and there was no way either @lucasmazza or myself could find a way to simulate the bug context. I extracted some of the code out of outdated into Definition and SpecSet and added unit specs to those extracted bits.
* Fix `outdated` listing regression from cc355865Lucas Mazza2016-10-281-2/+2
|
* filtered outdated msg shouldn't say 'up to date'chrismo2016-10-191-1/+13
| | | | | | | | | | Fixes #5076. When a filter option is in use and it filters out everything in the requested categories, it's safer to say there were no %{level} updates to display rather than "Bundle up to date!" Tracking an additional local variable with the exact info to know that even when filtered there was nothing to update anyway I didn't feel was worth it with the current design.
* Enable cons updates in outdated and other fixes.chrismo2016-10-121-9/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes #4772 - Changes previous `--patch` / `--minor` / `--major` options to `--filter-patch` / `--filter-minor` / `--filter-major` and adds back `--patch` / `--minor` / `--major` as conservative the patch level update options to match the behavior of these options in `bundle update` in 1.13. This is a breaking change for the previous filtering options added in 1.12, but we're allowing it because there was some confusion as to what those options did in 1.12, some thinking that it would perform the resolution constraints that these options _now_ actually do. A problem with merging in conservative bundle update options was the pre-existing `--strict` `outdated` option, which has been in `outdated` since 1.5. `--strict` for `outdated` means to only report on newer gem versions that still satisfy declared requirements in the Gemfile. Without `--strict`, `outdated` reports the most recent available regardless of declared requirements in the Gemfile. `--strict` in `update` in 1.13 means to not allow _any_ dependency to update past the patch level option. Rather than break the longer standing `--strict` option, the new `--update-strict` option has been added which maps to the conservative bundle update `--strict` option. We can revisit this in 2.0. This also fixes #5065, where the new filtering options were ignored if the `--strict` option was used.
* Better gem outdated list grouped by groups.Guillermo Guerrero2016-10-061-28/+71
| | | | | | | | | | | | Restore default outdated. Added command in cli: - bundle outdated --groups Added --group option. Groups with alphabetical order. Added test. Reverted.
* [Definition] Validate platform in addition to rubySamuel Giddins2016-08-251-1/+1
| | | | | # Conflicts: # lib/bundler/cli/doctor.rb
* Only report same platform gem updates for `bundle outdated`James Wen2016-04-251-2/+2
| | | | | | | | - `bundle outdated` will now only show updates for a gem if there are available updates for that gem on the same platform - ex. gem `laduradura` is being used on ruby platform but updates are available on gem `laduradura` for java platform = do not display potential update versions for java
* Rename `active_spec` to `active_specs` for points in execution where itJames Wen2016-04-251-4/+4
| | | | is an array of specs
* Fix `bundle outdated` with `--patch` and/or `--minor` forJames Wen2016-04-211-4/+9
| | | | | | non-semantically versioned gems - Examples of non-semantic versions: "7.0", "8"
* Allow `bundle outdated` to handle all combinations of `--major`,James Wen2016-03-271-4/+4
| | | | | | | `--minor`, and `--patch` flags - Add test coverage for these combination sets - Fixes #4396
* [RuboCop] Update to 0.38.0Samuel Giddins2016-03-091-3/+3
|
* Add `--patch` flag for `bundle outdated`James Wen2016-02-181-3/+11
| | | | | - `bundle outdated --patch` will only report updates in the patch version (v#.#.patch)
* Fix `--minor` flag behavior for `bundle outdated`James Wen2016-02-181-10/+21
| | | | | | - `bundle outdated --minor` should only report updates in the minor version (not "at least minor version") - Create shared example unit spec for ignoring major version updates
* Add error with message/explanation for `bundle outdated` in a frozen stateJames Wen2016-02-151-0/+14
| | | | | - (frozen state ex. after `bundle install --deployment`) - closes #4287
* Add --parseable (with --porcelain alias) to `bundle outdated` for minimal outputJames Wen2016-02-041-9/+23
| | | | | | | | | | | | | | | - This flag changes the output of bundle outdated from: ``` * activesupport (newest 3.0, installed 2.3.5, requested = 2.3.5) in groups "development, test" ``` to ``` activesupport (newest 3.0, installed 2.3.5, requested = 2.3.5)" ``` and removes the extraneous output relating to fetching gem metadata, version metadata, git updates, and resolving dependencies. - Addresses bundler/bundler-features#85
* Compatibility with frozen string literalsSamuel Giddins2016-01-311-0/+1
|
* bundle outdated with major and minor optionsCirdes Henrique2016-01-291-0/+12
| | | | | This feature adds the ability to specify on outdated command to show only the gems with a major or minor updates
* [RuboCop] Enable Style/PercentLiteralDelimitersSamuel Giddins2015-11-261-1/+1
|
* Fix Style/DeprecatedHashMethodsVictor Koronen2015-08-141-1/+1
|
* [RuboCop] Update to 0.33.0Samuel E. Giddins2015-08-071-1/+1
|
* Fix Style/SpaceInsideBlockBracesAndre Arko2015-07-181-4/+4
| | | | closes #3850
* [RuboCop] Enable Style/StringLiteralsSamuel E. Giddins2015-07-151-1/+1
|
* [RuboCop] Enable Style/SymbolProcSamuel E. Giddins2015-07-151-1/+1
|
* [RuboCop] Enable Style/EmptyLinesSamuel E. Giddins2015-07-151-1/+0
|
* show groups in non-verbose mode, fix NoMethodErrorAndre Arko2015-05-031-1/+1
|
* Clean up parallel installerAndre Arko2015-04-011-4/+4
|
* Update outdated.rbStefan Lance2015-03-301-2/+2
|
* Make `outdated` output more "grepable"Stefan Lance2015-03-271-0/+7
| | | | - Minimal solution
* Revert "svn source support"Andre Arko2015-01-251-4/+4
| | | | | | | | | | | | We're pulling out svn source support into a plugin. While we work on that, you can use the 1.8.0.svn release, but subversion sources aren't an official part of Bundler itself. This reverts commit 049d281d0fdcc29297a21c6a66cd7efc38690675. This reverts commit 22fecdd07fdf02edb1a8824fb73dd7e015507644. This reverts commit 38f195e11f37ce5139af4ff3384eb2f26c2edb19. This reverts commit 500436a33de0b884525dbf82cfc69332fc96f8b9. This reverts commit 2c356be90a23921058cd14fd0e4a366da195021a.
* Refine completion messagesAndre Arko2014-11-281-1/+1
| | | | | | | | Now that we’re printing the number of gems requested and installed in the bundle, it seems good to put those on the same line as the message that says “your bundle is complete!”. While we’re updating that message, it seems good to remove “your”, because it’s unclear whose bundle it is anyway. It’s just A Bundle, or The Bundle, which means we don’t need a pronoun or possessive.
* svn source supportStefan Huber2014-04-221-4/+4
|
* DB: Better outdated --strict.David Blondeau2014-01-261-7/+5
| | | | It now behaves exactly like if performing a dry run of `bundle update`
* whitespace styleAndre Arko2014-01-261-0/+1
|
* Removed trailing whitespacesSmit Shah2014-01-081-1/+1
|
* Refactored open and fixed few failing specsSmit Shah2014-01-081-2/+4
|
* Use *args instead of argsSmit Shah2014-01-081-1/+1
|
* Refactored init, check, install, update, show, outdated, cache andSmit Shah2014-01-081-0/+79
binstubs in CLI
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-15 19:12:40 +0000