Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub Pages build is broken #519

Closed
Haprog opened this issue Feb 14, 2024 · 0 comments · Fixed by #520
Closed

GitHub Pages build is broken #519

Haprog opened this issue Feb 14, 2024 · 0 comments · Fixed by #520

Comments

@Haprog
Copy link
Contributor

Haprog commented Feb 14, 2024

See failed build here https://github.com/solita/solita.github.com/actions/runs/7897753738

Probably caused by GitHub updating some dependencies of the built in Pages builder.
We can be more in control here by starting to use a custom GitHub Action to do the Jekyll build for generating and deploying GitHub Pages instead of using the current zero-config process.

Seems like these issues are related to the problem:

From what I understand it seems the issue manifests when using actions/jekyll-build-pages versions 1.0.10 or 1.0.11 (currently latest and default for GH pages classic build) but you could use older 1.0.9 via custom GH action. The open issue above is in the main jekyll repository so that Jekyll 3.9.4 and 3.9.5 apparently have some issue but that alone doesn't seem to cause the problem in this repo as even those versions seem to work fine in some situations (e.g. when testing locally). Maybe it's a combinations of dependencies that triggers the problem when using those latest versions of jekyll-build-pages.

Haprog added a commit to Haprog/solita.github.com that referenced this issue Feb 14, 2024
Adds a custom GitHub Action for Jekyll build to be used instead of the zero-config classic Pages build. This gives us more control over the build stack/dependencies. The Pages source needs to be configured in repository settings: Settings > Pages > Source: GitHub Actions.

Fixes solita#519
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant