Skip to content

Conversation

@admtnnr-huntress
Copy link
Contributor

@admtnnr-huntress admtnnr-huntress commented Aug 29, 2025

Description

This PR changes the base64 to require a minimum of 0.2.0 rather than only the 0.2.x line. We needed to relax this in order to update to 1.5.0 for the CA bundle updates as our application has a dependency on base64 version 0.3.0.

Motivation and Context

How Has This Been Tested?

Ran bundle exec rake test and ensured all tests were passing.

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

@admtnnr-huntress
Copy link
Contributor Author

@duo-lfalsetta it looks like you introduced the explicit base64 dependency recently. Can you let me know if there's something I can do to help ferry this along?

@duo-falsetta
Copy link
Contributor

@duo-lfalsetta it looks like you introduced the explicit base64 dependency recently. Can you let me know if there's something I can do to help ferry this along?

@admtnnr-huntress Apologies, I didn't really intend to make that dependency so strict, I just needed to ensure it was there because as of Ruby 3.4 it is no longer a default gem.

@duo-falsetta
Copy link
Contributor

duo-falsetta commented Oct 2, 2025

@admtnnr-huntress it appears that the option to allow the CI run has timed out. If you give things a little kick by pushing an empty commit (or something else like a no edit amend), the CI should retrigger and we can allow it to run.

@AaronAtDuo AaronAtDuo merged commit 912808d into duosecurity:master Oct 3, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants