jeffreytse/jekyll-deploy-action

Can't install the correct Bundler version

Open

#77 opened on Jan 31, 2024

View on GitHub
 (2 comments) (1 reaction) (1 assignee)Shell (48 forks)github user discovery
good first issue

Repository metrics

Stars
 (364 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I'm new to Jekyll and this GH Action, maybe I did something wrong, but if I got the docs right, then I should be able to define the right version in the workflow file and the action should use that version, no?

So I defined bundler_ver: '2.5.5' this but I still get this:

| Traceback (most recent call last):
|       2: from /usr/sbin/bundle:25:in `<main>'
|       1: from /usr/lib/ruby/2.7.0/rubygems.rb:296:in `activate_bin_path'
| /usr/lib/ruby/2.7.0/rubygems.rb:277:in `find_spec_for_exe': Could not find 'bundler' (2.5.5) required by your /home/florian/projects/jekyll/Gemfile.lock. (Gem::GemNotFoundException)
| To update to the latest version installed on your system, run `bundle update --bundler`.
| To install the missing version, run `gem install bundler:2.5.5`

Am I doing something wrong or is that a bug?

Contributor guide

Research direction
Investigate whether the GitHub Action correctly installs the specified bundler version. Check the Gemfile.lock and ensure the action's ruby version matches the required bundler version. Verify that the `bundler ver` input is properly passed to the gem install command.
Tech stack
shellruby
Domain
devopsci cd
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitJekyll basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70