README.md in bundleup-2.5.0 vs README.md in bundleup-2.5.1
- old
+ new
@@ -1,5 +1,9 @@
+📣 **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.
+
+---
+
# bundleup
[![Gem Version](https://img.shields.io/gem/v/bundleup)](https://rubygems.org/gems/bundleup)
[![Gem Downloads](https://img.shields.io/gem/dt/bundleup)](https://www.ruby-toolbox.com/projects/bundleup)
[![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/mattbrictson/bundleup/ci.yml)](https://github.com/mattbrictson/bundleup/actions/workflows/ci.yml)
@@ -104,31 +108,23 @@
if cli.updated_gems.any?
system "git commit -m \"Update gems dependencies\" -- Gemfile.lock"
end
```
-
## How bundleup works
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.)
Finally, bundleup runs `bundle outdated` to see the gems that were _not_ updated due to Gemfile restrictions.
After displaying its findings, bundleup gives you the option of keeping the changes. If you answer "no", bundleup will restore your original Gemfile.lock from its backup, leaving your project untouched.
## Roadmap
-bundleup is very simple at this point, but it could be more. Some possibilities:
+bundleup is in maintenance mode; no new features are planned.
-- Automatically commit the Gemfile.lock changes with a nice commit message
-- Integrate with bundler-audit to mark upgrades that have important security fixes
-- Display relevant CHANGELOG entries for major upgrades
-- Non-interactive mode
-
-If you have other ideas, open an issue on GitHub!
-
## Contributing
-Code contributions are also welcome! Read [CONTRIBUTING.md](CONTRIBUTING.md) to get started.
+Code contributions are welcome! Read [CONTRIBUTING.md](CONTRIBUTING.md) to get started.
[bundler]: http://bundler.io
[semver]: http://semver.org