diff options
| author | David RodrÃguez <deivid.rodriguez@riseup.net> | 2022-03-01 13:46:49 +0100 |
|---|---|---|
| committer | git <svn-admin@ruby-lang.org> | 2022-03-06 22:17:00 +0900 |
| commit | 156079a85d29a137521e6b911a39c25f35a960d2 (patch) | |
| tree | 285775d52f3f042a025d45937c850cd404864fc3 /lib/bundler/man/bundle-outdated.1 | |
| parent | 7cc0c53169759996f75eacd7cceb2ea8d47c57d7 (diff) | |
[rubygems/rubygems] Make `--strict` flag of `update` and `outdated` commands consistent
Previously they had slightly different behavior when combined with
conservative updating flags.
The correct behavior is the `--update-strict` option, so `--script` now
does that, The `--update-strict` option is left there for now but I will
deprecate it later.
https://github.com/rubygems/rubygems/commit/ab42046229
Diffstat (limited to 'lib/bundler/man/bundle-outdated.1')
| -rw-r--r-- | lib/bundler/man/bundle-outdated.1 | 13 |
1 files changed, 3 insertions, 10 deletions
diff --git a/lib/bundler/man/bundle-outdated.1 b/lib/bundler/man/bundle-outdated.1 index 459e0ce794..bb6149df34 100644 --- a/lib/bundler/man/bundle-outdated.1 +++ b/lib/bundler/man/bundle-outdated.1 @@ -1,13 +1,13 @@ .\" generated with Ronn/v0.7.3 .\" http://github.com/rtomayko/ronn/tree/0.7.3 . -.TH "BUNDLE\-OUTDATED" "1" "February 2022" "" "" +.TH "BUNDLE\-OUTDATED" "1" "March 2022" "" "" . .SH "NAME" \fBbundle\-outdated\fR \- List installed gems with newer versions available . .SH "SYNOPSIS" -\fBbundle outdated\fR [GEM] [\-\-local] [\-\-pre] [\-\-source] [\-\-strict] [\-\-parseable | \-\-porcelain] [\-\-group=GROUP] [\-\-groups] [\-\-update\-strict] [\-\-patch|\-\-minor|\-\-major] [\-\-filter\-major] [\-\-filter\-minor] [\-\-filter\-patch] [\-\-only\-explicit] +\fBbundle outdated\fR [GEM] [\-\-local] [\-\-pre] [\-\-source] [\-\-strict] [\-\-parseable | \-\-porcelain] [\-\-group=GROUP] [\-\-groups] [\-\-patch|\-\-minor|\-\-major] [\-\-filter\-major] [\-\-filter\-minor] [\-\-filter\-patch] [\-\-only\-explicit] . .SH "DESCRIPTION" Outdated lists the names and versions of gems that have a newer version available in the given source\. Calling outdated with [GEM [GEM]] will only check for newer versions of the given gems\. Prerelease gems are ignored by default\. If your gems are up to date, Bundler will exit with a status of 0\. Otherwise, it will exit 1\. @@ -28,7 +28,7 @@ Check against a specific source\. . .TP \fB\-\-strict\fR -Only list newer versions allowed by your Gemfile requirements\. +Only list newer versions allowed by your Gemfile requirements, also respecting conservative update flags (\-\-patch, \-\-minor, \-\-major)\. . .TP \fB\-\-parseable\fR, \fB\-\-porcelain\fR @@ -43,10 +43,6 @@ List gems from a specific group\. List gems organized by groups\. . .TP -\fB\-\-update\-strict\fR -Strict conservative resolution, do not allow any gem to be updated past latest \-\-patch | \-\-minor| \-\-major\. -. -.TP \fB\-\-minor\fR Prefer updating only to next minor version\. . @@ -77,9 +73,6 @@ Only list gems specified in your Gemfile, not their dependencies\. .SH "PATCH LEVEL OPTIONS" See bundle update(1) \fIbundle\-update\.1\.html\fR for details\. . -.P -One difference between the patch level options in \fBbundle update\fR and here is the \fB\-\-strict\fR option\. \fB\-\-strict\fR was already an option on outdated before the patch level options were added\. \fB\-\-strict\fR wasn\'t altered, and the \fB\-\-update\-strict\fR option on \fBoutdated\fR reflects what \fB\-\-strict\fR does on \fBbundle update\fR\. -. .SH "FILTERING OUTPUT" The 3 filtering options do not affect the resolution of versions, merely what versions are shown in the output\. . |