Issues with the new github-pages gem version 232

[arunk]

Select Topic Area

Bug

Body

Hi, so I have been working on this website and I started a couple of weeks ago and setup Jekyll and have been developing the site locally. I pushed the site to github a few times and it worked fine. But about a week ago, the github-pages gem seems to have changed in the default Jekyll builder, my local github-pages version is 231, but the github site appears to use 232. Now the site compiles fine with version 231 which I have installed locally, but it throws some error with version 232.
Specifically I'm seeing this error in the build logs:

Rendering Markup: assets/main.scss github-pages 232 | Error: String can't be coerced into Integer 

Now I tried to run bundle update in my local repo so I could update my github-pages gem and try and see where exactly this error was occurring. But running bundle update doesn't update the gem and running bundle update github-pages gives me this warning and doesn't update:

Using github-pages 231
Bundler attempted to update github-pages but its version stayed the same
Bundle updated!

I tried deleting Gemfile.lock and running bundle install and update again, but this is not updating. Could someone please help and let me know how to resolve this issue?

Oh I also fixed this issue temporarily by changing my Gemfile to this:

gem "github-pages", "~> 231", group: :jekyll_plugins

Explicitly setting the github-pages version. This appeared to work for a week or so, but as of today when I tried to push my repo, I get this warning:

The github-pages gem can't satisfy your Gemfile's dependencies. If you want to use a different Jekyll version or need additional dependencies, consider building Jekyll site with GitHub Actions: https://jekyllrb.com/docs/continuous-integration/github-actions/

followed by the build error above.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[arunk]

Finally managed to get the error in local server. Looked up the error and found that this has been happening for sometime now - https://answers.netlify.com/t/jekyll-builds-locally-but-jekylll-converter-errors-on-frontmatter-in-scss-in-netlify/33889 and sass/dart-sass#2045 . It is apparently random. I can confirm this, since I just did an empty push to the repo without changing anything and the repo built this time. In the 1 month that I've been working on the site in my local environment I haven't encountered the error even once, today was the first time. But on github.com i have encountered the error twice so far. Could someone please look into this issue?

[luannndev]

Hi arunk,

It looks like you're encountering an issue with the GitHub Pages gem and its compatibility with your local Jekyll setup. Here are some steps you can take to resolve the problem:

Update Your Gemfile: Since you're already using gem "github-pages", "~> 231", this should work with the previous version. However, if you want to update to the latest version, try changing your Gemfile to:

gem "github-pages", "~> 232", group: :jekyll_plugins
This will allow you to use the new version of the gem. After updating, run bundle update github-pages again.

Check Your Dependencies: The warning about not being able to satisfy your Gemfile's dependencies may indicate that other gems in your Gemfile are conflicting with the version of github-pages you want to use. Check the versions of all gems in your Gemfile and ensure they are compatible with the newer version of github-pages.

Clear Bundler Cache: Sometimes, clearing the Bundler cache can help resolve version issues. Run the following command:

bundle clean --force
Then, try running bundle install again.

Remove and Reinstall Gems: If the above steps do not work, consider removing the vendor/bundle directory and running bundle install again. This will force Bundler to fetch fresh copies of your gems.

Build with GitHub Actions: If you continue to encounter issues, consider building your Jekyll site using GitHub Actions as suggested in the warning. This way, you can customize your build environment and dependencies to avoid conflicts.

Check for Open Issues: Lastly, check the GitHub Pages repository for any open issues related to the version you're using. There might be others experiencing similar problems, and solutions may already be discussed there.

If you follow these steps and still face issues, feel free to provide more details about your Gemfile and the exact errors you’re encountering, and I’ll be happy to assist further!

[arunk]

Hi @luannndev thanks for your reply. As I mentioned in my 2nd post, this appears to be some weird bug in the the github-pages gem, that randomly occurs, it hadn't happened in my local development environment till now. And it appears to happen with both version 231 and 232. I will try your suggestion of clearing out all the bundler cache and doing a fresh install, but I suspect that will not fix the issue, because the same issue is there in Jekyll actions when Gtihub Pages tries to build the repository. There also it happens randomly. I have faced this issue twice so far in this repository. But after reading about this error being random I just pushed an empty commit to github to trigger the build process, and sure enough it worked without making any changes. So yes I suspect this might be a bug, thanks for pointing me to the Github Pages repository, I was looking for where Github pages repository is, but there are so many links related to Github pages and repositories that I wasn't able to find the right one. I'll probably report this issue there and see what they have to say.