Update Ruby gem and Github Actions packages#97
Merged
Conversation
Contributor
Author
|
@cederom this may also make it easier for you to build locally long as you have ruby >= 2.5 Note my instructions with the updated readme. |
Contributor
Cool! Thank you @btashton! :-) Yes we have ruby 3.0, 3.1, 3.2 on FBSD :-) I will verify and report back.. just need to take some sleep its 0530AM here :-P |
jerpelea
approved these changes
May 15, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This slims down and updates the Ruby gems that we are using. Removing the github-pages gem which was unused with they way that we upload the site meant we could move off a bunch of EOL gems and also on to the latest version on Jekell.
I did also have to update sass files, this was automated with sass-migrator https://sass-lang.com/documentation/cli/migrator
We are also running old versions of github actions which would spit out a warning about still using node 12. https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/
Impact
Living in the future.
Testing
Passing CI should be sufficient. Local testing also passed