Add Ruby 4.0 / Puppet 9 support - #418
Merged
Merged
Conversation
With the arrival of Puppetcore 9, we need to ensure our tools are compatible with Ruby 4. Adds a ruby_version: 4.0 / puppet_gem_version: ~> 9.0 lane to ci.yml and nightly.yml's spec and acceptance jobs. The Gemfile had no puppetcore-sourcing logic at all - it just used the default rubygems.org source unconditionally. Sources puppet from rubygems-puppetcore.puppet.com when a forge token is present, same pattern as rspec-puppet/puppetlabs_spec_helper.
puppet_litmus pulls in bolt as a transitive dependency, which otherwise resolves from rubygems.org (a stale 4.0.0 dragging in an old faraday/patron native-extension chain that fails to build - libcurl headers aren't present on the CI runner). Same fix as puppetlabs/provision.
david22swan
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With the arrival of Puppetcore 9, we need to ensure our tools are compatible with Ruby 4.
ruby_version: 4.0/puppet_gem_version: ~> 9.0lane to bothci.ymlandnightly.yml'sspecandacceptancejobs.puppetfromrubygems-puppetcore.puppet.comwhen a forge token is present (checking for a non-empty value specifically, sincegem_ci.ymlsets the env var even when no secret is configured), same pattern asrspec-puppet/puppetlabs_spec_helper.Verified locally: full spec suite passes (260 examples, 0 failures, 3 pre-existing pending unrelated to this change), rubocop clean.
Checklist