Bundler: Yanked check?
Open
Nobody has claimed this yet.
Bundler
- Dominant language
- Ruby
- Stars
- 4k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 81
Description
Describe the problem as clearly as you can
Right now, when a gem is yanked, if you have it locally or cached, you can still install it without warning.
It would be nice to have two features:
- bundle install should just warn on yanked gems
- a cli to check for are any gems yanked that CI checks can use
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 tracing Bundler's bundle install path and the existing CLI command entry points. Determine how locally available or cached gems are resolved, then define completion as a warning for yanked gems during installation and a CI-usable command that reports yanked gems.
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