Skip to content

Updates 'setup-ruby' to v1 in the Jekyll Workflow Template#3296

Open
eliduke wants to merge 1 commit into
actions:mainfrom
eliduke:patch-1
Open

Updates 'setup-ruby' to v1 in the Jekyll Workflow Template#3296
eliduke wants to merge 1 commit into
actions:mainfrom
eliduke:patch-1

Conversation

@eliduke
Copy link
Copy Markdown

@eliduke eliduke commented May 8, 2026

Recently started a new GitHub Pages / Jekyll project, and was surprised to see the setup-ruby action was still tied to a very old and specific version. Not sure why it's still held there, but I was getting some errors during my first couple deploys and I couldn't figure out what was going on!

I upgraded a bunch of my own personal projects to v1 a while back, and I had just assumed that the Jekyll workflow template would have been updated as well.

Thoughts? Concerns?

Recently started a new GitHub Pages / Jekyll project, and was surprised to see the setup-ruby action still tied to a very old and specific version. This is much cleaner now.
@eliduke eliduke requested review from a team as code owners May 8, 2026 20:28
@thatrobotdev
Copy link
Copy Markdown

I had the same issues! The workflow is currently pinned to setup-rubyv1207.0 which produces this error:

Using Bundler 4.0.1 from Gemfile.lock BUNDLED WITH 4.0.1
/opt/hostedtoolcache/Ruby/3.1.6/x64/bin/gem install bundler -v 4.0.1
ERROR:  Error installing bundler:
 bundler-4.0.1 requires Ruby version >= 3.2.0. The current ruby version is 3.1.6.

I tried upgrading incrementally:

So the minimum fix seems to be pinning to v1.177.0. We should also explicitly pin the runner to ubuntu-24.04 to prevent breakage in the future if we go this route.

@eliduke
Copy link
Copy Markdown
Author

eliduke commented May 25, 2026

Is there a need to pin it to a specific version beyond just v1? Doesn't that automatically pull the latest minor version as well?

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.

3 participants