Hi Scott, Jochen, Thanks for raising this on the list rather than letting it land quietly with the Jackson 3 move.
I agree the breakage around unquoted YAML 1.1-style scalars (`yes`/`no`/`on`/`off`, mixed-case booleans, `~`, octal/hex) needs to stay explicit for Groovy 7. Documenting it as a breaking change, pinning it with a test, and pointing at SnakeYAML for documents that still need the older typing looks like the right packaging for the default Jackson-based path. Jochen's point about not really landing on YAML 1.2 core either is fair; we should keep the release notes honest about what the resolver does and does not do. I am fine shipping with the documented behaviour if the guide and migration notes stay clear, and I am happy to review #2949 / GROOVY-12433 with that in mind. Cheers, Daniel Sun
