`gem install` should explain why it falls back to installing a version older than the latest
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 4k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 81
Description
I'm having a problem or would like to suggest a feature.
My current problem is that when installing a gem without specifying a version(in this case, fastlane gem) it would install 2.54.1 instead of 2.180.1 when determining the latest version.
This issue is related to:
- Network problems
- Installing a library
- Publishing a library
- The command line
gem - Other
Here are my current environment details:
$ gem env version
3.2.15
Checked with gem version 3.1.2 and install works as expected.
I will abide by the code of conduct.
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 by reproducing the report with gem install fastlane under gem version 3.2.15, then compare the result with gem version 3.1.2. Trace the gem install version-selection path and identify what fallback information is available; done means the command explains why it selected an older version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100