We had some .yml files that were saved with UTF8-BOM. These had worked for a long time, until they didn't - some time between 2019/06/04 and 2019/06/28 is when they stopped working.
We were getting the error /build/alpha.yml (Line: 1, Col: 1): Unexpected value 'trigger'. trigger wasn't actually the issue here - it was the BOMs at 1,1 that were causing things to break.
Was there an announcement that support for UTF8 w/ BOM would be dropped? If this was intentional, can a better error message be added? If this was not intentional, how are significant breaking changes like this slipping through?
In order to consolidate to fewer feedback channels, we've moved suggestions and issue reporting to Developer Community. Sorry for any confusion resulting from this move.
We had some .yml files that were saved with UTF8-BOM. These had worked for a long time, until they didn't - some time between 2019/06/04 and 2019/06/28 is when they stopped working.
We were getting the error
/build/alpha.yml (Line: 1, Col: 1): Unexpected value 'trigger'
.trigger
wasn't actually the issue here - it was the BOMs at 1,1 that were causing things to break.Specific files (and commit to fix the issue) that were encountering this issue: https://github.com/IntelliTect/Coalesce/commit/961fcd2cca2af6ff7b5a48bef7cca91ba1410709
Specific build that experienced this issue: https://intellitect.visualstudio.com/Coalesce/_build/results?buildId=5552&view=results
Was there an announcement that support for UTF8 w/ BOM would be dropped? If this was intentional, can a better error message be added? If this was not intentional, how are significant breaking changes like this slipping through?