@perdasilva why was the go directive bumped to 1.22.5? Did an underlying dependency require this change? Otherwise, I do not believe the semantics of the language changed between 1.22.0 and 1.22.5.

I believe if the goal were to ensure people who run this as the main module, then the go directive should have been kept as-is and toolchain go1.22.5 should have been added, instead.

Now, users who use this as a library instead of the main module are forced to bump their go.mod's go directive to go 1.22.5, which is disruptive