gem oauth2 v2.0.10 released
Photo (cropped) by Domino Studio on Unsplash I've just released oauth2 v2.0.10. It's a big release with many new features, and many bug fixes. But I'll save all that for later... Right now I want to talk about Upgrading. I know it is scary to upgrade something that will break horribly if it goes wrong. It's likely user facing. It may be hard to test outside production. This project sits underneath a large portion of the authorization systems on the internet. According to GitHub's project tracking, which I believe only reports on public projects, 100,000+ projects, and 500+ packages depend on this project. That is a lot of things to upgrade. That means it is painful for the Ruby community when this gem forces updates to its runtime dependencies. As a result, great care, and a lot of time, have been invested to ensure this gem is working with all the leading versions per each minor version of Ruby of all the runtime dependencies it can install with. What does that mean specifically for the runtime dependencies? We have 100% test coverage of lines and branches, and this test suite runs across a large matrix covering the latest patch for each of the following minor versions: MRI Ruby @ v2.3, v2.4, v2.5, v2.6, v2.7, v3.0, v3.1, v3.2, v3.3, v3.4, HEAD NOTE: This gem will still install on ruby v2.2, but vanilla GitHub Actions no longer supports testing against it, so YMMV. JRuby @ v9.2, v9.3, v9.4, v10.0, HEAD TruffleRuby @ v23.1, v23.2, HEAD gem faraday @ v0, v1, v2, HEAD gem jwt @ v1, v2, v3, HEAD gem logger @ v1.2, v1.5, v1.7, HEAD gem multi_xml @ v0.5, v0.6, v0.7, HEAD gem rack @ v1.2, v1.6, v2, v3, HEAD This gem follows a strict & correct (according to the maintainer of SemVer; more info) interpretation of SemVer. Dropping support for any of the runtime dependency versions above will be a major version bump. If you aren't on one of the minor versions above, make getting there a priority. You should upgrade this gem with confidence*. You should upgrade the dependencies of this gem with confidence*. Please do upgrade, and then, when it goes smooth as butter please sponsor me. Thanks! If you are thinking, "that list is missing two runtime dependencies", you are correct! Both of them were extracted from this gem. They are part of the oauth-xx org, and are developed in tight collaboration with this gem, so not much more needs to be said about them. gem snaky_hash - https://gitlab.com/oauth-xx/snaky_hash gem version_gem - https://gitlab.com/oauth-xx/version_gem * MIT license; I am unable to make guarantees.

Photo (cropped) by Domino Studio on Unsplash
I've just released oauth2 v2.0.10. It's a big release with many new features, and many bug fixes. But I'll save all that for later... Right now I want to talk about Upgrading. I know it is scary to upgrade something that will break horribly if it goes wrong. It's likely user facing. It may be hard to test outside production.
This project sits underneath a large portion of the authorization systems on the internet. According to GitHub's project tracking, which I believe only reports on public projects, 100,000+ projects, and 500+ packages depend on this project. That is a lot of things to upgrade.
That means it is painful for the Ruby community when this gem forces updates to its runtime dependencies.
As a result, great care, and a lot of time, have been invested to ensure this gem is working with all the leading versions per each minor version of Ruby of all the runtime dependencies it can install with.
What does that mean specifically for the runtime dependencies?
We have 100% test coverage of lines and branches, and this test suite runs across a large matrix covering the latest patch for each of the following minor versions:
- MRI Ruby @ v2.3, v2.4, v2.5, v2.6, v2.7, v3.0, v3.1, v3.2, v3.3, v3.4, HEAD
- NOTE: This gem will still install on ruby v2.2, but vanilla GitHub Actions no longer supports testing against it, so YMMV.
- JRuby @ v9.2, v9.3, v9.4, v10.0, HEAD
- TruffleRuby @ v23.1, v23.2, HEAD
- gem
faraday
@ v0, v1, v2, HEAD - gem
jwt
@ v1, v2, v3, HEAD - gem
logger
@ v1.2, v1.5, v1.7, HEAD - gem
multi_xml
@ v0.5, v0.6, v0.7, HEAD gem
rack
@ v1.2, v1.6, v2, v3, HEAD-
This gem follows a strict & correct (according to the maintainer of SemVer; more info) interpretation of SemVer.
- Dropping support for any of the runtime dependency versions above will be a major version bump.
- If you aren't on one of the minor versions above, make getting there a priority.
You should upgrade this gem with confidence*.
You should upgrade the dependencies of this gem with confidence*.
Please do upgrade, and then, when it goes smooth as butter please sponsor me. Thanks!
If you are thinking, "that list is missing two runtime dependencies", you are correct!
Both of them were extracted from this gem. They are part of the oauth-xx
org,
and are developed in tight collaboration with this gem, so not much more needs to be said about them.
- gem
snaky_hash
- https://gitlab.com/oauth-xx/snaky_hash - gem
version_gem
- https://gitlab.com/oauth-xx/version_gem
* MIT license; I am unable to make guarantees.