Repository navigation
Commit 58ae2da
committed
Add a test using setup-ruby twice in the same job
Using setup-ruby twice in the same job (e.g. for multiple Gemfiles in a
monorepo) was not tested, which let #444 slip through: BUNDLER_VERSION
exported by a first setup-ruby step using Bundler 1 leaked into a second
step, whose `bundle install` then failed with "You must use Bundler 2 or
greater with this lockfile".
The new job reproduces that scenario: a first step uses Bundler 1 via
gemfiles/bundler1.gemfile, then a second step on the root Gemfile must
use Bundler 2.4 (the latest Bundler for Ruby 2.7), both for the action's
own `bundle install` and for later steps.
It runs on ubuntu-24.04 since Ruby 2.7 is not available on ubuntu-26.04,
which ubuntu-latest is moving to.
Closes #4451 parent 26e5b7d commit 58ae2da
1 file changed
Lines changed: 24 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
358 | 358 | | |
359 | 359 | | |
360 | 360 | | |
| 361 | + | |
| 362 | + | |
| 363 | + | |
| 364 | + | |
| 365 | + | |
| 366 | + | |
| 367 | + | |
| 368 | + | |
| 369 | + | |
| 370 | + | |
| 371 | + | |
| 372 | + | |
| 373 | + | |
| 374 | + | |
| 375 | + | |
| 376 | + | |
| 377 | + | |
| 378 | + | |
| 379 | + | |
| 380 | + | |
| 381 | + | |
| 382 | + | |
| 383 | + | |
| 384 | + | |
361 | 385 | | |
362 | 386 | | |
363 | 387 | | |
| |||
0 commit comments