ruby / ruby/rubygems

bundle outdated should check if bundler is outdated

Open
#3,297 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bundler type: feature request
Dominant language
Ruby
Stars
4k
Forks
1.9k
Avg merge
1d 2h
Merged PRs (30d)
81

Description

bundle outdated does a great job of checking the Gemfile.lock for outdated dependencies. It doesn't check if bundle itself is outdated, though

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the bundle outdated command and inspect how it checks dependencies in Gemfile.lock. Look for existing tests covering this command and determine how Bundler's own version should be compared. Done means bundle outdated also reports when Bundler itself is outdated.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.