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

Upgrade Ruby to 3.3 and Jekyll to 4.3 #1192

Merged
merged 1 commit into from
Dec 13, 2024

Conversation

Fryguy
Copy link
Member

@Fryguy Fryguy commented Dec 13, 2024

Jekyll comes with the jekyll-sass-converter plugin, so most of the work in this commit is switching to that gem, which expects an _sass directory by default. Also, that gem does not support sprockets, so we need to do some manual handling of the various sass gems to include their stylesheets and other assets (fonts) in the proper directories.

Fixes #878

@jrafanie Please review.

This should also end up closing some renovate PRs

@Fryguy Fryguy added enhancement dependencies Pull requests that update a dependency file labels Dec 13, 2024
@Fryguy Fryguy force-pushed the upgrade_jekyll_ruby branch from 7a0ab3d to 102979f Compare December 13, 2024 16:10
Jekyll comes with the jekyll-sass-converter plugin, so most of the work
in this commit is switching to that gem, which expects an _sass
directory by default. Also, that gem does not support sprockets, so we
need to do some manual handling of the various sass gems to include
their stylesheets and other assets (fonts) in the proper directories.

Fixes ManageIQ#878
@Fryguy Fryguy force-pushed the upgrade_jekyll_ruby branch from 102979f to b00bde9 Compare December 13, 2024 16:13
Copy link
Member

@jrafanie jrafanie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome! 2.7 to 3.3 is quite a jump.

This looks great. For followup, does it make sense to checkin a Gemfile.lock for this project? I know some of them were created before Gemfile.lock worked well cross-platform so maybe that's why we don't have it. Just a thought. Not sure if it makes sense.

@jrafanie jrafanie merged commit b641e33 into ManageIQ:master Dec 13, 2024
2 checks passed
@Fryguy Fryguy deleted the upgrade_jekyll_ruby branch December 13, 2024 16:29
Fryguy added a commit to Fryguy/manageiq-documentation that referenced this pull request Dec 19, 2024
Fryguy added a commit to Fryguy/guides that referenced this pull request Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade Website to use Jekyll 4.x instead of current 3.x
2 participants