Pages build and deployment warnings

[FeedFoodie]

Select Topic Area

Question

Body

The terminal shows that every gem is updated and nothing is missing, but I still get the following warnings whenever I update my site:

Warning: the running version of Bundler (2.1.4) is older than the version that created the lockfile (2.4.19). We suggest you to upgrade to the version that created the lockfile by running gem install bundler:2.4.19.
Resolving dependencies...
The following gems are missing

• minitest (5.20.0)
• activesupport (7.0.8)
• addressable (2.8.5)
• base64 (0.1.1)
• execjs (2.9.1)
• commonmarker (0.23.10)
• faraday (2.7.11)
• rexml (3.2.6)
• mini_portile2 (2.8.4)
• nokogiri (1.15.4)
• webrick (1.8.1)
  Install missing gems with bundle install
  Warning: github-pages can't satisfy your Gemfile's dependencies.

How do I fix this?

[MaryaBaloch20]

The warning message you're receiving indicates that the version of Bundler currently installed on your system (2.1.4) is older than the version of Bundler that was used to create the Gemfile.lock file (2.4.19). This can potentially lead to dependency issues when you try to update gems.

To resolve this issue and ensure your gems are properly updated, you should upgrade Bundler to the version specified in your Gemfile.lock. Here are the steps to do that:

1. Check the Bundler Version in Gemfile.lock:

Open your Gemfile.lock file and look for a line that specifies the Bundler version. It should look something like this:

BUNDLED WITH
2.4.19

2. Upgrade Bundler:

Open your terminal and run the following command to upgrade Bundler to the version specified in your Gemfile.lock:

gem install bundler:2.4.19
Make sure to replace 2.4.19 number with the version number you found in your Gemfile.lock

3. Update Gems:

After upgrading Bundler, navigate to your project directory and run:

bundle update

4. Install Missing Gems:

If you still see missing gem warnings after running bundle update, install the missing gems as suggested in the warning message:

bundle install

[FeedFoodie]

Thanks for the quick reply. I have done what you said 5-6 times before making my post and it did not work.

gem list bundler
*** LOCAL GEMS ***

bundler (default: 2.4.19)

bundle install
Bundle complete! 10 Gemfile dependencies, 94 gems now installed.
Use bundle info [gemname] to see where a bundled gem is installed.

bundle update
Fetching gem metadata from https://rubygems.org/...........
Resolving dependencies...
Bundle updated!

According to the terminal, everything has been updated, but the github workflow log still shows the same warning.

[MaryaBaloch20]

It appears that you have successfully updated your local Bundler version to match the version specified in your Gemfile.lock (2.4.19) and have updated your gems using bundle update. However, you are still encountering the same warning in your GitHub workflow.

To resolve this issue, you should make sure that your GitHub Actions workflow is also using the updated version of Bundler. Here are the steps to ensure this:

Update Bundler Version in GitHub Actions Workflow:

Locate your GitHub Actions workflow file (typically named .github/workflows/your_workflow.yml) in your repository.

Inside the workflow file, you can add a step to ensure the correct version of Bundler is used. You can specify the Bundler version in a jobs section of your workflow like this:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Set up Ruby
        uses: actions/setup-ruby@v1
        with:
          ruby-version: 2.x # Replace with your Ruby version
          bundler-cache: true

      - name: Use Ruby and Bundler version from Gemfile.lock
        run: |
          bundle config path vendor/bundle
          bundle install --jobs 4 --retry 3
        env:
          BUNDLER_VERSION: 2.4.19 # Set the desired Bundler version

      - name: Build and test
        run: |
          bundle exec jekyll build # Replace with your build command
        env:
          JEKYLL_ENV: production

Replace 2.x with your desired Ruby version and update the BUNDLER_VERSION to match the version specified in your Gemfile.lock.

Commit and Push Changes:

Save the changes to your workflow file, commit the changes, and push them to your GitHub repository.

Trigger the GitHub Workflow:

Once you've pushed the changes, GitHub Actions should automatically run your updated workflow with the correct Bundler version.

By specifying the Bundler version in your GitHub Actions workflow, you ensure that the correct version is used during the workflow, which should resolve the warning you were seeing.

[chrisdel101]

Did U solve this? I have the same issue.

[FeedFoodie]

Yes, by creating a custom workflow instead of using the default for github pages. It takes twice as much time to deploy now but I no longer see errors.

Refer to: https://jekyllrb.com/docs/continuous-integration/github-actions/

# Sample workflow for building and deploying a Jekyll site to GitHub Pages
name: Deploy Jekyll site to Pages

on:
  # Runs on pushes targeting the default branch
  push:
    branches: ["gh-pages"]

  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:

# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
  contents: read
  pages: write
  id-token: write

# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:
  # Build job
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4
      - name: Setup Ruby
        uses: ruby/setup-ruby@8575951200e472d5f2d95c625da0c7bec8217c42 # v1.161.0
        with:
          ruby-version: '3.2.2' # Not needed with a .ruby-version file
          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
          cache-version: 0 # Increment this number if you need to re-download cached gems
      - name: Setup Pages
        id: pages
        uses: actions/configure-pages@v5
      - name: Build with Jekyll
        # Outputs to the './_site' directory by default
        run: bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}"
        env:
          JEKYLL_ENV: production
      - name: Upload artifact
        # Automatically uploads an artifact from the './_site' directory by default
        uses: actions/upload-pages-artifact@v3

  # Deployment job
  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4