pipelines-schema.json: in-step condition and clone not recognized by YAML ext

[Oleksii Mudryk]

YAML extension using pipelines-schema.json and shows clone and condition properties inside step item as invalid.
At the same time, online validator shows this as valid. Moreover, the pipelines work perfectly and as expected with this these properties - work only on condition and take only configured clone depth or do not clone if disabled.

(see screenshot, see attached file)

‌

[Scott Digiambattista]

I’m having this issue as well

[Andrés Soria]

Same with runs-on property

‌

[Sebastian Fredriksson Bernholtz]

This relates to https://bitbucket.org/atlassianlabs/atlascode/issues/66/yaml-validator-inconsistent-with-online and https://bitbucket.org/atlassianlabs/atlascode/issues/536/bitbucket-pipeline-yaml-schema-property.