You're right. I'm afraid there was a testing failure in this case. All
the gfns had been tested probably a day before the March 29 change,
and at the time it didn't seem that anything "significant" had changed
between then and the April 5 release. But that's a risky assumption,
and not one I'll make in future. Obviously, it would be good if I were
not the only person testing all the gfns' sample scripts in the run-up
to a release.

It is not difficult to setup automatically to run the tests. We have the GitHub project ready, to do so. We only need to have the tests prepared so that they don't have hardcoded paths (I did found references to your Allin's home path.).

You can see an example of the GitHub Actions configuration here: https://github.com/gretl-project/gretl/blob/3628e810c1ae30e005ddc97b784b7ea936a13457/.github/workflows/build_and_test.yml

And the Actions execution, here: https://github.com/gretl-project/gretl/actions
(they fail, because the setup is to use SonaCloud but Gretl does not have it done. We can use the other file, build_and_test.yml , but we need to have your tests prepared.)