fix: old LSP version hardcodes flow schema version

Mikołaj Wawrzyniakrequested to merge
mwaw/ignore_schema_version_check_for_legacy_flows into main

What does this merge request do and why?

fix: old LSP version hardcodes flow schema version

Because old LSP versions hardcodes Flow Registry schema version as experimental, it prevents migration to v1, without indroduction of a breaking change. To avoid that, this change overrides flow schema version field with value sorced from config for legacy lsp versions

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request checklist

  • Tests added for new functionality. If not, please raise an issue to follow up.
  • Documentation added/updated, if needed.
  • If this change requires executor implementation: verified that issues/MRs exist for both Go executor and Node executor or confirmed that changes are backward-compatible and don't break existing executor functionality.

Merge request reports