Skip to content

Use a bundler default that works with Ruby 3.3 - #40

Merged
jablan merged 1 commit into
mainfrom
fix/bundler-default-ruby-3.3
Oct 28, 2026
Merged

jablan merged 1 commit into
mainfrom
fix/bundler-default-ruby-3.3

Conversation

@jablan

@jablan jablan commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

Problem

d2b8506 set the default Ruby of lawa-ci, lawa-report and the lawa-*-ci workflows to 3.3, but the default ruby-bundler-version is still 2.1.4 (2.3.14 for elixir). bundler 2.1.4 crashes on Ruby 3.3 (SystemStackError: stack level too deep when running lawa), so any caller relying on the defaults fails the license check. Callers on ubuntu-26.04 also can't fall back to the old Ruby 3.1.x defaults, since no 3.1.x is built there.

Change

  • Default ruby-bundler-version to 2.5.23 in lawa-ci, lawa-report, lawa-js-ci, lawa-npm-ci and lawa-elixir-ci. lawa-ruby-ci already defaults to 2.5.4.
  • README: update the documented ruby/bundler defaults for the section I touched.

Callers that pass ruby-bundler-version explicitly are unaffected.

Follow-up

  • v1/v2 tags still point at older commits (v1 pins setup-ruby v1.178.0, which fails on ubuntu-26.04). A release/tag move is needed for consumers using @v1; not done here.
  • phrase/strings-openapi currently works around this with a SHA pin and explicit ruby-bundler-version (build(API): fix CI on ubuntu-26.04 runners strings-openapi#1351); a follow-up there will drop it once this is released.

🤖 Generated with Claude Code

The Ruby default is now 3.3, but the bundler default was still 2.1.4 (2.3.14
for elixir), which crashes with SystemStackError on Ruby 3.3. Bump to 2.5.23.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant