You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue to for people looking for information about build errors they may be getting from GitHub actions as of January 2025+.
The default "jekyll.yml" starter workflow in existing projects is broken!
Due to changes in the ubuntu-latest image, the GitHub Action will end up with errors in existing repositories. Note that we do not maintain the "jekyll.yml" or GitHub Actions so can not directly fix the default starter workflow.
To fix it in your project, edit the file ".github/workflows/jekyll.yml" in your repository.
On line 37, replace: uses: ruby/setup-ruby@8575951200e472d5f2d95c625da0c7bec8217c42 # v1.161.0
with: uses: ruby/[email protected]
This should fix the error!
The text was updated successfully, but these errors were encountered:
The default "jekyll.yml" has been fixed as of 2025-01-14, so for NEW collections going forward, setting up GitHub Actions should be working again.
However, EXISTING collections using the default "jekyll.yml" GitHub Action to build may still be impacted! If you have an existing collection getting build errors from GitHub Actions, update as mentioned above ^
This issue to for people looking for information about build errors they may be getting from GitHub actions as of January 2025+.
The default "jekyll.yml" starter workflow in existing projects is broken!
Due to changes in the ubuntu-latest image, the GitHub Action will end up with errors in existing repositories. Note that we do not maintain the "jekyll.yml" or GitHub Actions so can not directly fix the default starter workflow.
To fix it in your project, edit the file ".github/workflows/jekyll.yml" in your repository.
On line 37, replace:
uses: ruby/setup-ruby@8575951200e472d5f2d95c625da0c7bec8217c42 # v1.161.0
with:
uses: ruby/[email protected]
This should fix the error!
The text was updated successfully, but these errors were encountered: