bundleup 2.5.0 → 2.5.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +6 -10
- data/lib/bundleup/version.rb +1 -1
- metadata +3 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 9309396a42a834ecdea275abdbaba14fc4a9ad93106a1b64df45aa6c993eb64b
|
4
|
+
data.tar.gz: f80c20abfc9b599245fbd253a120437720d6132288982fe6743023aa40c3b304
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 6078c4c847d5cc66a84769e97115cbd2ac49bda66b0efa5f77f1a45e6aee339b5e5d916f53f13f1af02e8b1377b014aac073be2832ec33326bf9dbd05e7aa337
|
7
|
+
data.tar.gz: 3f5ed2747c5c426139c228ee72b075e2769038a5fd1b7a9adb99909736987d8e929b9df083bf034c34f37bb36f83c06034df4adc56996e2824b089b24da02a81
|
data/README.md
CHANGED
@@ -1,3 +1,7 @@
|
|
1
|
+
📣 **I am no longer actively developing this project.** I am focusing my attention on building [mattbrictson/bundle_update_interactive](https://github.com/mattbrictson/bundle_update_interactive) instead. It has many of the same features as `bundleup`, so please check it out! In the meantime, `bundleup` will continue to receive occasional maintenance, but likely no new capabilities.
|
2
|
+
|
3
|
+
---
|
4
|
+
|
1
5
|
# bundleup
|
2
6
|
|
3
7
|
[![Gem Version](https://img.shields.io/gem/v/bundleup)](https://rubygems.org/gems/bundleup)
|
@@ -106,7 +110,6 @@ if cli.updated_gems.any?
|
|
106
110
|
end
|
107
111
|
```
|
108
112
|
|
109
|
-
|
110
113
|
## How bundleup works
|
111
114
|
|
112
115
|
bundleup starts by making a backup copy of your Gemfile.lock. Next it runs `bundle check` (and `bundle install` if any gems are missing in your local environment), `bundle list`, then `bundle update` and `bundle list` again to find what gems versions are being used before and after Bundler does its updating magic. (Since gems are actually being installed into your Ruby environment during these steps, the process may take a few moments to complete, especially if gems with native extensions need to be compiled.)
|
@@ -117,18 +120,11 @@ After displaying its findings, bundleup gives you the option of keeping the chan
|
|
117
120
|
|
118
121
|
## Roadmap
|
119
122
|
|
120
|
-
bundleup is
|
121
|
-
|
122
|
-
- Automatically commit the Gemfile.lock changes with a nice commit message
|
123
|
-
- Integrate with bundler-audit to mark upgrades that have important security fixes
|
124
|
-
- Display relevant CHANGELOG entries for major upgrades
|
125
|
-
- Non-interactive mode
|
126
|
-
|
127
|
-
If you have other ideas, open an issue on GitHub!
|
123
|
+
bundleup is in maintenance mode; no new features are planned.
|
128
124
|
|
129
125
|
## Contributing
|
130
126
|
|
131
|
-
Code contributions are
|
127
|
+
Code contributions are welcome! Read [CONTRIBUTING.md](CONTRIBUTING.md) to get started.
|
132
128
|
|
133
129
|
[bundler]: http://bundler.io
|
134
130
|
[semver]: http://semver.org
|
data/lib/bundleup/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: bundleup
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 2.5.
|
4
|
+
version: 2.5.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Matt Brictson
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2024-
|
11
|
+
date: 2024-10-15 00:00:00.000000000 Z
|
12
12
|
dependencies: []
|
13
13
|
description: Use `bundleup` whenever you want to update the locked Gemfile dependencies
|
14
14
|
of a Ruby project. It shows exactly what gems will be updated with color output
|
@@ -63,7 +63,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
63
63
|
- !ruby/object:Gem::Version
|
64
64
|
version: '0'
|
65
65
|
requirements: []
|
66
|
-
rubygems_version: 3.5.
|
66
|
+
rubygems_version: 3.5.21
|
67
67
|
signing_key:
|
68
68
|
specification_version: 4
|
69
69
|
summary: A friendlier command-line interface for Bundler’s `update` and `outdated`
|