v2.0

This is the first release by @etagwerker and the FastRuby.io team! ICYMI: https://www.fastruby.io/blog/railsbump-maintained-by-fastruby-io.html 🚀

Top Changes

1. Compatibility check is now using GitHub Actions to try to bundle install with a specific gem and a specific Rails release
2. We are sharing more details about why a gem is compatible or not with a Rails release (for example: https://www.railsbump.org/gems/sqlite/compatibility/rails-4-1)
3. We fixed an issue that happened when trying to check a lockfile with a gem that was not accessible (#109)

What's Changed

This section was auto-generated by GitHub:

• Add exception if gem is not found by @alexeyschepin in #61
• Fix links in email by @ShockwaveNN in #67
• Migrate from SQLite to Postgres (Heroku), Envkey to Dotenv, by @etagwerker in #82
• Bump actions/checkout from 2 to 4 by @dependabot in #83
• Add comments to Compats::Check by @manuelmeurer in #85
• Do not require unnecessary components by @etagwerker in #86
• Add rails release details to the rails releases table by @etagwerker in #89
• Trigger Github checks via Github API instead of commits + Refactor checks by @manuelmeurer in #84
• Update Ruby Releases in Database by @etagwerker in #93
• Remove support sections by @manuelmeurer in #98
• Better error pages by @etagwerker in #100
• Fixes/alerts_flashes by @etagwerker in #99
• Add sitemap_generator support and configuration by @etagwerker in #102
• New Rails Compatibility Page by @etagwerker in #103
• Redirect to existing slug when Gemfile.lock content has been already processed by @etagwerker in #105
• Case-insensitive gem search by @trusche in #107
• Add support for inaccessible gemmies by @etagwerker in #109

New Contributors

• @ShockwaveNN made their first contribution in #67
• @trusche made their first contribution in #107

Full Changelog: v1.0...v2.0