@hsbt after the release of 1.6.0 it seems there is still a segfault, but now it reproduces in this repo's tests: https://github.com/ruby/syck/actions/runs/28084164414/job/83145978245
@hsbt after the release of 1.6.0 it seems there is still a segfault, but now it reproduces in this repo's tests: https://github.com/ruby/syck/actions/runs/28084164414/job/83145978245