Skip to content

cloudsmith_release: make ruby_version configurable, bump default to JRuby 10 + bundler 2.7.2 - #91

Open
tungleduyxyz wants to merge 1 commit into
mainfrom
jruby10-cloudsmith-bump
Open

tungleduyxyz wants to merge 1 commit into
mainfrom
jruby10-cloudsmith-bump

Conversation

@tungleduyxyz

Copy link
Copy Markdown
Contributor

Summary

Companion PR to killbill-admin-ui-standalone's JRuby 10 upgrade, which uses this shared cloudsmith_release.yml workflow (via snapshot_release.yml, with_ruby: 'true') to build/release its WAR.

  • Add a ruby_version input (defaulting to jruby-10.0.6.0, the JRuby 10 LTS line) so callers can override the JRuby version used when with_ruby is true, instead of it being hardcoded to jruby-9.4.15.0.
  • Bump the paired gem install bundler step to 2.7.2 to match JRuby 10.0.x's bundled bundler version.

killbill-admin-ui-standalone's snapshot_release.yml already pins jdk: '21' explicitly for its own JDK setup step, so this change is independent of (and doesn't conflict with) the separate in-progress java21 branch that changes this workflow's jdk input default.

Re-applies #88 (reverted by #89).

Note

No functional change for any other caller of this reusable workflow: the new ruby_version input defaults to the JRuby 10 LTS version, but existing callers that don't set with_ruby: 'true' are unaffected, and any caller relying on the exact old default can pin ruby_version: 'jruby-9.4.15.0' explicitly if needed.

…Ruby 10 + bundler 2.7.2

Add a ruby_version input (defaulting to jruby-10.0.6.0, the JRuby 10 LTS line) so callers can override the JRuby version used when with_ruby is true, instead of it being hardcoded to jruby-9.4.15.0. Bump the paired bundler install to 2.7.2 to match JRuby 10.0.x's bundled bundler version.

Used by killbill-admin-ui-standalone's snapshot_release.yml, which already pins jdk: '21' explicitly for its own JDK setup step (unaffected by this repo's jdk input default).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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