bundle update <gem> should say when it could not update to latest
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 4k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 81
Description
A few times already I did bundle update faraday for example just for it to do nothing then I have to hop over to rubygems to check what the latest is or go through the Gemfile.lock to see who is locking it.
It would be great to either have bundle update faraday --force-latest and then fail/explain "Version 1.2.3 could not be installed because " or have the regular bundle update faraday say updated faraday to 1.0.0 (cannot update to 1.2.3 because of foobar dependency)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the bundle update faraday command and inspect how it compares the resolved version with the latest available version and reports results. Use the Gemfile.lock dependency constraints as the example case; done means the command clearly explains when the latest version cannot be selected and why.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100