Kothapalli Venkata Avinash
11/24/2025, 3:44 PMkapa.ai
11/24/2025, 3:45 PMCatalogParser with the explicit message: > You must upgrade your platform version to use this connector version. Either downgrade your connector or upgrade platform to 0.63.7.[\[Postgres issue\]](https://github.com/airbytehq/airbyte/issues/54691); [\[BigQuery issue\]](https://github.com/airbytehq/airbyte/issues/59702) From the linked, already-resolved Postgres issue, the situation is: - When you re-host official connector images in a private registry (ECR, GCR, etc.) and create a custom connector definition pointing to that image, Airbyte still enforces the same minimum platform version requirement that is encoded in the connector’s metadata.[\[Postgres issue\]](https://github.com/airbytehq/airbyte/issues/54691) - Newer destination connector versions (especially those using the latest Typing & Deduping) require at least Airbyte platform 0.63.7. If the platform is older (for example, 1.1.0 Helm install which uses an older internal “platform version”), you get this exact error at sync time, while the connection test can still pass.[\[Postgres issue\]](https://github.com/airbytehq/airbyte/issues/54691); [\[BigQuery issue\]](https://github.com/airbytehq/airbyte/issues/59702) In the open BigQuery issue, the user tried to work around this by: - Building a custom BigQuery destination image off Airbyte’s code. - Adding an older connector version (2.8.2) to definition_version and toggling supports_refreshes, but they still get the same platform error.[\[BigQuery issue\]](https://github.com/airbytehq/airbyte/issues/59702) This indicates that simply editing DB records or re-tagging the image does not bypass the platform requirement check performed by the connector code itself (CatalogParser.toStreamConfig).[\[BigQuery issue\]](https://github.com/airbytehq/airbyte/issues/59702) Given the information in the issues, your realistic options are: 1. Upgrade Airbyte platform to ≥ 0.63.7 This is what the error and both issues explicitly recommend and is the supported path when you want to run the latest destination connector versions.[\[Postgres issue\]](https://github.com/airbytehq/airbyte/issues/54691); [\[BigQuery issue\]](https://github.com/airbytehq/airbyte/issues/59702) 2. Downgrade the destination connector versions you mirror into your private registry - Choose a connector version that is known to work with your current platform (i.e., one that does not include the newer T&D features requiring 0.63.7). - In the closed Postgres issue, using the built‑in connector definition with the same version works, but the custom re-hosted one fails if the version is too new. That implies you must pick a version that is compatible with your platform, not just re-host the latest tag.[\[Postgres issue\]](https://github.com/airbytehq/airbyte/issues/54691) - The BigQuery issue shows that simply copying a version from a newer platform branch (like v0.63.7’s metadata.yaml) and adding it manually is not sufficient to avoid the error.[\[BigQuery issue\]](https://github.com/airbytehq/airbyte/issues/59702) 3. Use the built-in connector definitions instead of custom ones, where possible - In the Postgres case, the built‑in destination-postgres with the same version does not produce the error, while the custom definition using the same image but different registry does.[\[Postgres issue\]](https://github.com/airbytehq/airbyte/issues/54691) - This suggests that if company policy allows, sticking to built-in definitions can avoid some of the mismatches you are seeing. Because the knowledge sources don’t include a definitive matrix of “connector version X ⇔ minimum platform version Y”, I can’t tell you exactly which older BigQuery / Postgres destination versions will work with your current deployment. The only explicit information present is that the versions you are currently using require platform 0.63.7 or higher, and that overriding DB metadata alone does not change that.[\[Postgres issue\]](https://github.com/airbytehq/airbyte/issues/54691); [\[BigQuery issue\]](https://github.com/airbytehq/airbyte/issues/59702) Summary of recommended action based on the issues: - If you want to keep using the latest destination connectors from your private registry, upgrade your Airbyte platform to at least 0.63.7. - If you cannot upgrade the platform, mirror an older, compatible connector version into your private registry and point your custom connector definition to that version instead of the latest one. - Avoid relying on DB hacks (definition_version edits) to bypass this; the enforcement is happening in the connector code.Kothapalli Venkata Avinash
11/24/2025, 3:49 PMkapa.ai
11/24/2025, 3:49 PMkapa.ai
11/24/2025, 3:49 PMCatalogParser) because the connector version you’re running declares a minimum platform version of 0.63.7 (internal platform versioning), and your current setup is below that requirement.[[BigQuery issue](https://github.com/airbytehq/airbyte/issues/59702); [Postgres issue](https://github.com/airbytehq/airbyte/issues/54691)] Key points from the linked issues: - The error is thrown at runtime in destinations: ConfigErrorException: You must upgrade your platform version to use this connector version. Either downgrade your connector or upgrade platform to 0.63.7.[[BigQuery issue](https://github.com/airbytehq/airbyte/issues/59702)] - It only appears during sync/write, not during “Test connection,” which matches what you describe (issues only with destinations).[[Postgres issue](https://github.com/airbytehq/airbyte/issues/54691)] - Re‑hosting images in a private registry or manually tweaking DB metadata (e.g., definition_version, supports_refreshes) does not bypass this; the check is embedded in the connector JAR and triggered by the catalog parsing logic.[[BigQuery issue](https://github.com/airbytehq/airbyte/issues/59702)] Given what’s in the sources, your options are: 1. Upgrade the Airbyte platform to meet the connector’s minimum platform version (the error explicitly asks for ≥ 0.63.7).[[BigQuery issue](https://github.com/airbytehq/airbyte/issues/59702)] 2. Downgrade destination connector versions you mirror to your private registry to ones that don’t enforce this newer Typing & Deduping requirement. The closed Postgres issue confirms that newer destination versions can fail on older platforms, while compatible versions work fine.[[Postgres issue](https://github.com/airbytehq/airbyte/issues/54691)] 3. Where possible, use the built‑in destination definitions instead of custom/private-registry ones; in the Postgres case, the built‑in connector with the same version worked, while the custom one failed.[[Postgres issue](https://github.com/airbytehq/airbyte/issues/54691)] The knowledge sources do not specify exactly which connector versions are guaranteed to work with 1.2.0, only that the versions you are currently using require a higher platform level and thus fail with that specific destination error.