Skip to content

CI against Ruby 3.4 and 4.0#446

Open
y-yagi wants to merge 5 commits intoShopify:mainfrom
y-yagi:ci_against_latest_rubies
Open

CI against Ruby 3.4 and 4.0#446
y-yagi wants to merge 5 commits intoShopify:mainfrom
y-yagi:ci_against_latest_rubies

Conversation

@y-yagi
Copy link

@y-yagi y-yagi commented Jan 29, 2026

What are you trying to accomplish?

Currently, packwerk doesn't run tests against the latest Rubies(3.4 and 4.0). This PR adds them to the CI matrix.

What approach did you choose and why?

I added Ruby 3.4 and 4.0 to the CI matrix.
But, it seems that CI is broken. So I added some commits to fix the broken CI, too.

What should reviewers focus on?

Type of Change

  • Bugfix
  • New feature
  • Non-breaking change (a change that doesn't alter functionality - i.e., code refactor, configs, etc.)

Additional Release Notes

  • Breaking change (fix or feature that would cause existing functionality to change)

Include any notes here to include in the release description. For example, if you selected "breaking change" above, leave notes on how users can transition to this version.

If no additional notes are necessary, delete this section or leave it unchanged.

Checklist

  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • It is safe to rollback this change.

y-yagi and others added 5 commits January 29, 2026 07:50
prism requires its own builder class in order to emit ast for
versions that the parser gem doesn't support. The next prism
version will warn when a incorrect builder class is used,
it wasn't previously enforced.
`minitest/mock` has been extracted to the `minitest-mock` gem since
minitest v6.0.0.
@y-yagi y-yagi requested a review from a team as a code owner January 29, 2026 01:56
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.

2 participants