Skip to content

Run tests against Ruby 3.3 - #11767

Closed
jturel wants to merge 4 commits into
Katello:masterfrom
jturel:test_ruby_33
Closed

Run tests against Ruby 3.3#11767
jturel wants to merge 4 commits into
Katello:masterfrom
jturel:test_ruby_33

Conversation

@jturel

@jturel jturel commented May 28, 2026

Copy link
Copy Markdown
Member

What are the changes introduced in this pull request?

Considerations taken when implementing this change?

What are the testing steps for this pull request?

@coderabbitai

coderabbitai Bot commented May 28, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d95151c7-9026-4652-8883-c1933b7c2627

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@ofedoren ofedoren left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @jturel, it's nice to see green CI here without any changes needed :) Although, CI might not catch all :/

Anyway, I only have one concern: we need to run on both Ruby 3.0 and Ruby 3.3. The Set became part of standard lib in Ruby 3.2 only, so 3.0 still requires us to explicitly require 'set' . Even though it seems fine, I'd rather be paranoid and add those statements where we actually call Set.new (app/services/katello/product_content_finder.rb#L29, app/services/katello/registration_manager.rb#L71) or maybe include it somewhere else, so we require it before it gets used.

s.email = ["ericdhelms@gmail.com", "walden@redhat.com"]
s.homepage = "https://github.com/Katello/bastion"
s.license = "GPL-2.0-or-later"
s.gem.required_ruby_version = ['>= 2.5.0', '< 2.7.0']

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not related to this PR, but that's weird. Is .gem. really needed? All the other gemspecs have s.required_ruby_version...

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty sure we don't need the gemspec at all since bastion is now loaded as an engine and we don't build it as a gem..

@ofedoren

ofedoren commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Or, since those are not necessary changes, we can leave those statements (they are harmless), but add TODO comment, something like Drop when Ruby 3.2 is the new minimum.

@sjha4

sjha4 commented Jun 10, 2026

Copy link
Copy Markdown
Member

I have borrowed the commits from this PR and added a small change to remove the bastion gemspec which is legacy code in this PR here: #11778. Thanks @jturel , @ofedoren .. ❤️

@sjha4 sjha4 closed this Jun 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants