jeffreytse/jekyll-deploy-action

Sudden step failure without any change

Open

#60 opened on Feb 19, 2023

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Shell (48 forks)github user discovery
help wanted

Repository metrics

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

Description

Starting yesterday, this step for my project began failing on installing nokogiri:

An error occurred while installing nokogiri (1.10.10), and Bundler cannot
continue.

In Gemfile:
  rails was resolved to 6.1.7.2, which depends on
    actioncable was resolved to 6.1.7.2, which depends on
      actionpack was resolved to 6.1.7.2, which depends on
        actionview was resolved to 6.1.7.2, which depends on
          rails-dom-testing was resolved to 2.0.3, which depends on
            nokogiri

This happened without any change to my repo, so I'm assuming there was an upstream change that caused the failure? Did I miss a deprecation or mandatory upgrade?

Contributor guide

Research direction
Investigate the cause of nokogiri installation failure in the GitHub Actions workflow. Check if the nokogiri gem version 1.10.10 is outdated or incompatible with the current environment. Look for recent changes to the base Docker image or Ruby version. Consider updating the Gemfile to use a newer version of nokogiri or specify platform specific options. Also check the repository's Actions logs for additional clues.
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.
1-3 hours
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
GitRubyBundlerGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55