Skip to content

(CAT-2724) Add ruby_version input to acceptance and mend reusable workflows - #183

Merged
imaqsood merged 1 commit into
mainfrom
add-ruby-version-param
Aug 4, 2026
Merged

imaqsood merged 1 commit into
mainfrom
add-ruby-version-param

Conversation

@imaqsood

@imaqsood imaqsood commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Summary

module_ci.yml already accepts a ruby_version input, but module_acceptance.yml and mend_ruby.yml hardcoded ruby-version: "3.1". This adds the same input to those two reusable workflows so callers can select the Ruby version, defaulting to '3.1' to preserve current behaviour.

Jira: CAT-2724

Why

Puppet 9 modules require Ruby >= 3.2 at bundle time (facterdb ~> 3.1, Puppet 9 lint tooling). With Ruby pinned to 3.1, the acceptance Setup Test Matrix and the Mend jobs fail during bundle lock:

Bundler found conflicting requirements for the Ruby version:
  Ruby (>= 3.2.0)
  Current Ruby version:
    Ruby (= 3.1.7)

Changes

  • module_acceptance.yml — add ruby_version input (default: '3.1'); use it in both ruby/setup-ruby steps (the setup_matrix job and the acceptance test job).
  • mend_ruby.yml — add ruby_version input (default: '3.1'); use it in the setup-ruby step.

Default unchanged → existing callers unaffected. Puppet 9 modules opt in with ruby_version: "3.2".

Testing

Consumed from puppetlabs-inifile (MODULES-11703) pinned to this branch with ruby_version: "3.2":

  • Acceptance Setup Test Matrix now bundles on Ruby 3.2 (previously failed on 3.1).
  • Callers that don't set the input are unaffected (still Ruby 3.1).

🤖 Generated with Claude Code

@imaqsood
imaqsood requested review from a team as code owners August 4, 2026 14:52
    Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@imaqsood
imaqsood force-pushed the add-ruby-version-param branch from 87f26a7 to 9c0af81 Compare August 4, 2026 16:49
@imaqsood
imaqsood merged commit e88b20f into main Aug 4, 2026
3 checks passed
@imaqsood
imaqsood deleted the add-ruby-version-param branch August 4, 2026 17:02
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