zalando / zalando/zalando.github.io

pages build step "Build with Jekyll" emits warnings about bundler

Open
#447 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
111
Forks
37
PR merge metrics
No merged PRs in 30d

Description

Task Headline

https://github.com/zalando/zalando.github.io/actions/runs/6625406926/job/17996328161

Warning: the running version of Bundler (2.1.4) is older than the version that created the lockfile (2.3.26). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.3.26`.
The following gems are missing
 * minitest (5.19.0)
 * activesupport (7.0.6)
 * execjs (2.8.1)
 * ffi (1.15.5)
 * faraday (2.7.10)
 * nokogiri (1.15.3)
 * parallel (1.23.0)
 * rainbow (3.1.1)
 * yell (2.2.2)
 * zeitwerk (2.6.[11](https://github.com/zalando/zalando.github.io/actions/runs/6625406926/job/17996328161#step:4:12))
 * html-proofer (4.4.3)
 * webrick (1.8.1)
Install missing gems with `bundle install`
Warning:  github-pages can't satisfy your Gemfile's dependencies.
To use retry middleware with Faraday v2.0+, install `faraday-retry` gem
        Pagination: Pagination is enabled, but I couldn't find an index.html page to use as the pagination template. Skipping pagination.

Seems that it's also related to the action itself https://github.com/actions/jekyll-build-pages/issues/104.

Expected delivery

Builds pass w/o warnings.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the referenced GitHub Actions run and the “Build with Jekyll” step, then compare its Bundler and Gemfile dependency warnings with the linked jekyll-build-pages issue. Determine whether the warnings are caused by this repository or the action itself; done means the Pages build passes without warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, jekyll
Domain
build-system, ci-cd, documentation
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.