Skip to content

Conversation

@jeremyevans
Copy link
Collaborator

@searls I think things are ready for a new release. I'm not sure what the historical release process is. If you want to handle the release, that works for me. If you want to add me as an owner in rubygems and for me to handle it, I can take care of it. If there any specific release process instructions I should handle, please let me know.

@jeremyevans jeremyevans requested a review from searls December 4, 2025 01:23
@jeremyevans
Copy link
Collaborator Author

@searls I'd like to get m 1.7.0 released in the next week, so it is available by the Ruby 4.0.0 release. In addition to Ruby 4.0 support and dropping of the method_source dependency, support has been added for minitest 6 (released yesterday).

@searls
Copy link
Collaborator

searls commented Dec 19, 2025

@searls I'd like to get m 1.7.0 released in the next week, so it is available by the Ruby 4.0.0 release. In addition to Ruby 4.0 support and dropping of the method_source dependency, support has been added for minitest 6 (released yesterday).

Great! I added you as an owner of the gem (something I am actually authorized to do)

@jeremyevans
Copy link
Collaborator Author

Thank you! I'll merge this now and handle the release this evening.

@jeremyevans jeremyevans merged commit bf9728d into qrush:master Dec 19, 2025
22 checks passed
@jeremyevans
Copy link
Collaborator Author

m 1.7.0 released! Note that after I worked on all of these changes, I found out that minitest 6 ships with a minitest program that allows native testing by line number, so if you are using minitest 6, you don't need to use m (though m has the benefit of being shorter).

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.

2 participants