Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

Update bundle lock with conservative update behavior/options #4912

Closed
chrismo opened this issue Aug 24, 2016 · 0 comments
Closed

Update bundle lock with conservative update behavior/options #4912

chrismo opened this issue Aug 24, 2016 · 0 comments

Comments

@chrismo
Copy link
Contributor

chrismo commented Aug 24, 2016

Task spawned from #4676.

Suggested by @JuanitoFatas in livingsocial/bundler-patch#34, we should investigate getting bundle lock in sync with bundle update --patch and --minor behavior.

chrismo added a commit to chrismo/bundler that referenced this issue Oct 4, 2016
Fix rubygems#4912.

The bundle lock command produces a lockfile same as bundle update but
won't install all the gems. If the `--update` option is fed to `bundle
lock` you can also specify the `--patch`, `--minor`, `--major` and
`--strict` options added to `bundle update` in 1.13.
@homu homu closed this as completed in #5045 Oct 4, 2016
homu added a commit that referenced this issue Oct 4, 2016
Add conservative update options to bundle lock

Fix #4912.

The bundle lock command produces a lockfile same as bundle update but
won't install all the gems. If the `--update` option is fed to `bundle
lock` you can also specify the `--patch`, `--minor`, `--major` and
`--strict` options added to `bundle update` in 1.13.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant