-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Ruby 3.4 #26
base: master
Are you sure you want to change the base?
Support Ruby 3.4 #26
Conversation
The warning that appears without this change is: warning: base64 was loaded from the standard library, but is not part of the default gems starting from Ruby 3.4.0. You can add base64 to your Gemfile or gemspec to silence this warning.
Co-authored-by: Étienne Barrié <[email protected]>
9012527
to
5a2962c
Compare
FYI, have been running this branch in production on Ruby 3.4.1 without issue for a day or so now. |
👋 @anakinj, is this something you'd be able to look into reviewing, merging, and releasing? (tagging as I see you've been active over in jwt/ruby-jwt) |
Hi. I'd love to help but I don't currently have powers to merge or release the jwe gem. I'll reach out to @francescobbo to see if he would be willing to extend the powers a bit. |
Disclaimer: I'm not that familiar with this gem. Simply trying to address Ruby 3.4 issues as it will be released in a few days and the amount of warning messages when running our application on Ruby 3.4 is quite large. Thankfully the fixes seem pretty straightforward.
base64
to the Gemspec as a runtime dependency as it's no longer a default gem as of Ruby 3.4.frozen_string_literal: true
directive anddup
all strings that we attempt to modify in place withforce_encoding
as in place string modification is forbidden with said directive in place.Resolves #25