spectral: Error: Mapping key must be a string scalar rather than number

Looking for a way to turn off that error caused by OAS response code keys that the linter interprets as numbers. It’s kind of misleading, and in large specs it produces a lot of useless report lines. I can’t find anything in docs about disabling the errors generated by parser.

petstore.txt linter_report.txt

Thanks

P.S. Looks like key validation logic was recently introduced in @spectral/yaml in https://github.com/stoplightio/yaml/commit/2712bee8ef672127ade17c3d6d17a9771383f532 and the workaround is to roll back to 3.4.0 version of @spectral/yaml.