Let's go, Pikachu! It's 0.10 and Ruby 3.x time

[apjanke]

This issue is to track my work on getting a v0.10 release out. Milestone is 0.10.1. (Because there was a bogus 0.10.0 published, so can't use that x.y.0 version.)

My plan is to roll up all the bug fixes and features which have already been merged to master or are "90%" there, bump all the gem deps, and make a new release with that, without waiting for any other pending features or bugfixes.

Important fixes needed:

• libxml 2.10+ compatibility for <dot.> and <foo:colon> angle-bracket syntax #102
• RPM build failure on Fedora 39/Rawhide (bc nokogiri libxml "foo:colon" thing) #107
• Failed to install ronn-ng because of ruby 3 #100
• Gobble up n-ronn fixes for 0.10.1 #87
• HTML-style comment causes RuntimeError #65

Let's also do:

• Add prerelease Homebrew formula, for testing that packaging
  • Done in apjanke/homebrew-ronn-ng@f3ce694
• Test 0.10.1 prerelease on Intel Mac
  • Install Homebrew on angharad, and switch to new dotfiles

Then:

• Publish golden 0.10.1 release
  • Done: Ronn-NG 0.10.1 on GitHub Releases

See the 0.10.1 milestone for more issues.

Hope to satisfy:

• Revert \(bu to \[ci] change #51 (comment)

[apjanke]

Work note:

Created a new WIP/lets-go-pikachu-0.10 branch for this work leading up to an 0.10 release. Working off the doc-project/Developer-Guide.md file for doing this release.

The ronn-ng.gemspec and other files currently have "0.10.1.pre3" as their version. Bumped that to "0.10.1.pre4". I don't recall there being an 0.10.0 release, but if there's documentation in the repo of it, I'm gonna defer to that. (And the CHANGES file says that was a RubyGems publishing oopse; that sounds pretty plausible.)

To bump the deps, I deleted Gemfile.lock locally and then ran bundle install.

Got to the "Regenerate the man pages with bundle exec rake man" step in the build process, and hit this, on angharad, my Mac desktop:

$ bundle exec rake man
env: ruby3.2: No such file or directory

I'm not sure what this means. Why does rake man know to call ruby3.2 instead of plain ruby? And why don't I have that on my machine? Nothing in the source code seems to be specifying Ruby 3.2 per se.

[ronn-ng] $ pwd
/Users/janke/repos/ronn-ng
[ronn-ng] $ grep -r 3\\.2 .
./Gemfile.lock:    parser (3.2.2.4)
./Gemfile.lock:    rexml (3.2.6)
./Gemfile.lock:      parser (>= 3.2.1.0)
[ronn-ng] $

Anyway, doesn't look like I have Ruby 3.2 here. This is on my macOS 14 Sonoma box "angharad", using MacPorts.

[ronn-ng] $ which ruby
/usr/bin/ruby
[ronn-ng] $ ruby --version
ruby 2.6.10p210 (2022-04-12 revision 67958) [universal.x86_64-darwin23]
[ronn-ng] $ port installed | grep ruby
  ruby30 @3.0.6_0 (active)
  ruby_select @1.3_1 (active)
[ronn-ng] $

Guess I need to install Ruby 3.2, and also figure out how to better get the ruby calls in this build script to detect ruby and its versions?

[apjanke]

Looks like Ruby 3.2 is available in MacPorts as the ruby32 package. did a port install ruby32 on angharad.

That took a while. Apparently it has a dependency on rust, and that's a big compile? Waiting for it to finish. I'll post an update tomorrow.

[apjanke]

I built and published 0.10.1.pre4 and pre6 releases. Tests are passing on Fedora using the new "test against RPM supplied dependency gems" technique described here (dd2ceeb). All the bugs in the 0.10.1 milestone are closed. Going to publish it today.

[apjanke]

All done here, I think! I published the 0.10.1 release on GitHub Releases and on RubyGems just now.

[apjanke]

For future reference, here's a copy of my local notes for this task.

ronn-ng 23Q4 fixup notes.md