Investigate Bundler 2.5.12 failures
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 873
- Forks
- 164
- Avg merge
- 4d 27m
- Merged PRs (30d)
- 9
Description
Limiting the bundler version isn't a long term solution.
CI: https://github.com/Shopify/tapioca/actions/runs/9519041069
Was able to reproduce one test locally: bin/test spec/tapioca/cli/gem_spec.rb:706 for https://github.com/Shopify/tapioca/blob/a983c8456771bdb1bbbf860202fad63b63387308/spec/tapioca/cli/gem_spec.rb#L706
Edit: Still happening on 2.5.15: https://github.com/Shopify/tapioca/actions/runs/9958874529
Contributor guide
No contributing guide indexed for this repository
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 CI run and reproduce the failure using bin/test spec/tapioca/cli/gem_spec.rb:706, comparing the reported Bundler 2.5.12 and 2.5.15 behavior. Trace the failing test and the version-limiting change in PR 1923. Done means the failure's cause and a durable resolution are identified rather than relying on a Bundler pin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100