Add dependencies to quiet warnings and prepare for Ruby 3.5 #255
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #250
Checklist
Added changelog entry (If there isn't an
#unreleasedsection, add that and your changelog entry to the top of the changelog)Ran unit tests (
rake test:unit):Note: to get the tests to run on Ruby 3.2 and 3.3, i had to temporarily remove the
require "pry"line from spec/spec_helper.rb. That change is not part of this PR because its part of the larger issue of getting the tests working on modern, maintained Ruby versions. I also don't know if pry is still required for integration tests, so i didn't want to remove it. All unit tests passed on Ruby 3.2 and 3.3. Testing on Ruby 3.4 succeeded except for two trivial failures related to expecting the old representation of hashes (i.e.{:a => "b"}as opposed to{a: "b"}I alphabetized all attributes, parameters, and methods by name in any class file I changed
I have linked the JIRA ticket in the summary section
not applicable
I have reviewed the JIRA ticket to ensure all AC's are met
not applicable
I understand that unless this is a Draft PR or has a DO NOT MERGE label, this PR is considered to be in a deploy ready state and can be deployed if merged to main