Update Ruby version for documentation generation (2.7.6 is end-of-life)

[filmaj]

If you go to build the documentation locally, following the directions in the maintainer's guide (.github/maintainers_guide.md), you will see warnings in your console like so:

➜ bundle install
rbenv: version `2.7.6' is not installed

➜ rbenv install 2.7.6
To follow progress, use 'tail -f /var/folders/k0/mp_cy45d7h7btpfxd62q16dc0000gq/T/ruby-build.20240607085431.58478.log' or pass --verbose
Downloading openssl-1.1.1w.tar.gz...
-> https://dqw8nmjcqpjn7.cloudfront.net/cf3098950cb4d853ad95c0841f1f9c6d3dc102dccfcacd521d93925208b76ac8
Installing openssl-1.1.1w...
Installed openssl-1.1.1w to /Users/fmaj/.rbenv/versions/2.7.6

Downloading ruby-2.7.6.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.6.tar.bz2
Installing ruby-2.7.6...

WARNING: ruby-2.7.6 is nearing its end of life.
It only receives critical security updates, no bug fixes.


WARNING: ruby-2.7.6 is past its end of life and is now unsupported.
It no longer receives bug fixes or critical security updates.

Perhaps it is as simple as updating the ruby version in the docs/.ruby-version file, but haven't tried myself. We should fix this!

[zimeg]

This EOL has bugged me but we might be fixed to 2.7.x by github pages. It's unclear to me if this dependency actually needs to be fixed or set though 🤔

That page links to a few other resources that don't mention a fixed Ruby v2, so maybe bumping to the latest is alright? Here are some of those interesting links:

• https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll#installing-jekyll
• https://jekyllrb.com/docs/continuous-integration/github-actions/

The Github actions page is interesting since a migration is happening that requires pages be built in actions, but we're already doing that here so it might be no worry:

All GitHub Pages builds will use GitHub Actions from June 30, 2024.

Just sharing thoughts and info since I haven't tried upgrading this either 😅

[github-actions]

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.