Update jwt to 3.2.0 for CVE-2026-45363#124
Conversation
|
RbNaCl/libsodium is used by the google provider, but indirectly so as long as the google api gems support jwt >= 3 we should be good. |
|
Checked commit Fryguy@1f148ed with ruby 3.3.10, rubocop 1.86.0, haml-lint 0.73.0, and yamllint 1.37.1 |
|
Embedded Terraform specs pass locally with an overridden oci gem |
|
@miq-bot cross-repo-test IBM/ruby-sdk-core#47, agrare/oci-ruby-sdk@bump_jwt |
|
@miq-bot cross-repo-test manageiq-providers-ibm_cloud, manageiq-providers-google, including IBM/ruby-sdk-core#47, agrare/oci-ruby-sdk@bump_jwt |
|
@miq-bot cross-repo-test manageiq-providers-ibm_cloud, manageiq-providers-google, manageiq-providers-oracle_cloud including IBM/ruby-sdk-core#47, agrare/oci-ruby-sdk@bump_jwt |
@agrare Please review.
Here's the information about upgrading to 3.x: https://github.com/jwt/ruby-jwt/blob/main/UPGRADING.md, however I don't think it affects anything in this repo.
The bigger problem is that the oci gem also depends on 2.x, so we;re going to have to find a way to upgrade that one.