diff options
| author | Bundlerbot <bot@bundler.io> | 2019-12-15 13:25:17 +0000 |
|---|---|---|
| committer | Bundlerbot <bot@bundler.io> | 2019-12-15 13:25:17 +0000 |
| commit | 683fe9799e37bff81e53f1a7e97d3a19896b8fc9 (patch) | |
| tree | 94b2370a0b229af606696ba900254e28cf95f0ed /man/bundle-lock.1 | |
| parent | 9e06edc33f7f1e8eeec370ff33a279b4d9bd1b9b (diff) | |
| parent | c40d5e15898ae5679f89969ec22a2efb9b4f68c4 (diff) | |
| download | bundler-2.1.0.tar.gz | |
Merge #7479v2.1.0
7479: Get ready for 2.1.0 release r=deivid-rodriguez a=deivid-rodriguez
### What was the end-user problem that led to this PR?
The problem was we want to release bundler 2.1.0 before ruby 2.7.0 ships, so that bundler 2.1.0 can be included with ruby 2.7.0.
### What is your fix for the problem, implemented in this PR?
My fix is to get ready for the release.
Co-authored-by: Bundlerbot <bot@bundler.io>
Co-authored-by: David RodrÃguez <deivid.rodriguez@riseup.net>
Diffstat (limited to 'man/bundle-lock.1')
| -rw-r--r-- | man/bundle-lock.1 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/man/bundle-lock.1 b/man/bundle-lock.1 index 6b86531f60..b64a645eb8 100644 --- a/man/bundle-lock.1 +++ b/man/bundle-lock.1 @@ -1,7 +1,7 @@ .\" generated with Ronn/v0.7.3 .\" http://github.com/rtomayko/ronn/tree/0.7.3 . -.TH "BUNDLE\-LOCK" "1" "November 2019" "" "" +.TH "BUNDLE\-LOCK" "1" "December 2019" "" "" . .SH "NAME" \fBbundle\-lock\fR \- Creates / Updates a lockfile without installing |