-
Notifications
You must be signed in to change notification settings - Fork 28
chore: update all dependencies (major) #707
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
base: main
Are you sure you want to change the base?
chore: update all dependencies (major) #707
Conversation
Summary of ChangesHello @renovate-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on maintaining the project's dependencies by upgrading the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request updates minitest to version 6, a major release with numerous breaking changes. This update is likely to cause failures in your test suite if minitest is in use. It is critical to thoroughly run all tests and adapt any existing test code to the new Minitest v6 API before merging. If minitest is no longer a direct dependency for your tests, consider removing it from the Gemfile altogether.
|
|
||
| group :development, :test do | ||
| gem "minitest", "~> 5.0" | ||
| gem "minitest", "~> 6.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This major version upgrade to minitest v6 introduces significant breaking changes that will likely break your test suite. According to the official release notes, some of the breaking changes include:
- Dropped support for Ruby versions below 3.0.
Minitest::Unit::TestCasehas been removed (useMinitest::Test).assert_nothing_raisedhas been removed (useassert_silent).assert_raisesnow requires an exception class to be specified.
Before merging, please ensure that the entire test suite is executed and passes. If minitest is not actively used, it would be better to remove this dependency rather than update it.
11dd0d7 to
ea6304d
Compare
This PR contains the following updates:
"~> 5.0"→"~> 6.0"3.4.7→4.0.0Release Notes
minitest/minitest (minitest)
v6.0.1Compare Source
v6.0.0Compare Source
ruby/ruby (ruby)
v4.0.0: 4.0.0See also:
What's Changed
#io_writehook on IO flush by noteflakes · Pull Request #15609--with-ext=when ENABLE_SHARED=yes: ruby/digest.h not found for rubyspec CAPI extensions - Ruby - Ruby Issue Tracking SystemNote: This list is automatically generated by tool/gen-github-release.rb. Because of this, some commits may be missing.
Full Changelog
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.