Update oauth gem from 0.5.8 to 0.5.9

[CloCkWeRX]

ruby-oauth/oauth@v0.5.8...v0.5.9

Should be safe, but... Its a lot!

[CloCkWeRX]

Claude review:
Assess ruby-oauth/oauth@v0.5.8...v0.5.9

Synthesized release notes distinguishing tooling updates from functional changes
Synthesized release notes distinguishing tooling updates from functional changes
Between v0.5.8 (2021‑11‑10) and v0.5.9 (2022‑05‑03) of ruby-oauth/oauth, there were no functional or behavioral code changes — the release was entirely maintenance/tooling work in preparation for wrapping up the 0.5.x series. Per the project's changelog, v0.5.9 included:

Documentation improvements related to Ruby compatibility
CHANGELOG.md formatting and typo fixes
CI build hardening
Requiring MFA to push new gem versions to RubyGems (release-process security, not library security)
Replacing Hash Rocket syntax (:key => value) with JSON-style symbol syntax (key: value) where possible — a cosmetic/rubocop-driven internal cleanup
General project tooling prep (adding rubocop-ruby2_0, overcommit) ahead of the final 0.5.x release
Bottom line: this is a low-risk, no-behavior-change bump. There's nothing here that fixes a bug, patches a security issue, or alters the public API — it's essentially a housekeeping release. Safe to take with no code changes required on your end.

One thing worth flagging since it's relevant either way: this is quite an old part of the gem's history. The project has since moved well past 0.5.x — current changelog shows it's up to v1.1.8 (July 2026), and notably v1.1.6 contains an actual security fix (GHSA-pp92-crg2-gfv9, hardening OAuth token endpoint redirect handling against cross-origin redirects). If you're evaluating this gem for current use rather than auditing history, it'd be worth checking whether you're on a version at or after 1.1.6.