Jedr Blaszyk

@vim345 I see you were doing some work on coverage badge, is that expected for now?

Putting as medium effort as we need to think if proposed version compatibiltiy matrix makes sense

Duplicate of: https://github.com/elastic/connectors/issues/930

> I love this issue to add compatibility checks ❤️ Have we considered also adding a periodic runtime check (not only at startup)? For example, what if the user upgraded...

I reproduced the issue: - Create new cloud deployment `

> curl command workaround to add the field Verified that following command fixes the bug for subsequent syncs ``` PUT .elastic-connectors-sync-jobs-v1/_mapping { "properties": { "job_type": { "type": "keyword" } }...

> scan our migrations to see if this same mistake has occurred elsewhere since we moved our index definitions to templates in Elasticsearch I took the mappings diff between index...

Sharing requests that should be added in the migration to update the mappings, I will followup to add this to 8.14 migration logic Connector index ``` PUT .elastic-connectors-v1/_mapping { "properties":...

`ent-search` module would take care of updating the mappings when migration to ES `8.14+` this issue should be fixed going forward