Tidy the project, and prepare for another release.

[flavorjones]

Mechanize hasn't gotten much love lately. I'm opening this issue to track some things I'd like to do, and to solicit input from the current maintainers (it's been a while since I've been involved).

Higher priority:

• move to Github Actions for CI. Travis doesn't seem to be building anymore, and I'm unsure of the long-term status (ci: replace travis with github actions #561)
• get master green (test: conditionally skip depending on net-http-persistent < v4 #558, Add webrick to development dependecies #557, Make JRuby green #562)
• generate a CVE for save/load in Mechanize::CookieJar has OS Command Injection #547 and merge Prevent OS command injection #548 to address it (similar to CVE-2019-5477 - Nokogiri Command Injection Vulnerability nokogiri#1915)
  • see GHSA-qrqm-fpv6-6r8g
• cut security release v2.7.7

Lower priority:

• drop support for EOLed Rubies (< 2.5), update required_ruby_version
• add Rubocop's security checks to CI (which will only run after dropping support for 1.9)
• update gem dependency versions
• review current PRs for low-hanging fruit to merge
• freshen up the README
• cut release v2.8.0

Would there be objections if I spent some of my hacking time getting through this list?

[flavorjones]

OK, no comments, then I intend to proceed!

[ddoherty03]

Does it make sense to ensure the gem is compatible with Ruby3?

[flavorjones]

@ddoherty03 Without knowing what you're seeing, I can't be sure I'm answering your question. But I can say that the master branch now has webrick added as a dependency and so should work on Ruby 3 with the next release. Is that helpful? If not, can you ask a more specific question?

[flavorjones]

Release v2.7.7 has been shipped.

[flavorjones]

For the remaining items, I've created issues and a milestone:

• drop support for EOLed Rubies (< 2.5) · Issue #563 · sparklemotion/mechanize
• add Rubocop's security checks to CI · Issue #564 · sparklemotion/mechanize
• update gem dependency versions · Issue #565 · sparklemotion/mechanize
• freshen up the README · Issue #566 · sparklemotion/mechanize
• v2.8.0 Milestone

And I'll be flagging PRs with the milestone if I think we can easily get them in.

[flavorjones]

@ddoherty03 v2.7.7 just shipped which should support Ruby 3. If you're still experiencing problems, can you open a new issue to discuss it? Thank you!

[ddoherty03]

Yes, all good now on the Ruby3 front, for me anyway. Thanks @flavorjones.