@kapa.ai regarding this issue https://github.com/airbytehq/airbyte/issues/73326 After the first import should i upgrade back to the newest version?

The knowledge sources don’t mention issue

#73326

specifically, nor do they describe a workflow where you must downgrade, import, and then re-upgrade in that exact pattern, so I can’t give a definitive “yes, that’s required” based on them. What they do say: • When upgrading Airbyte (especially on Kubernetes/Helm), you should follow the documented upgrade path and avoid very large version jumps; incremental upgrades may be needed in some cases.[Upgrading Airbyte][Syncs upgrade gap] • During an upgrade, Airbyte may update some connector versions automatically, but used connectors are not auto-upgraded; you manage those manually via the UI.[Upgrading Airbyte] • For connector updates, you should: ◦ Review the changelog and migration guide. ◦ Manually upgrade major versions. ◦ Optionally pin versions if you can’t update yet.[Connector updates] Given that, the docs generally recommend running on a supported/latest version and managing connector versions carefully, but they do not explicitly say you must immediately upgrade back to the newest platform version right after a first import used as a workaround. So, based only on the available docs: • It is recommended to be on a current, supported Airbyte version and to follow the documented upgrade procedure when you move back up. • There is no explicit requirement in the docs that after a first import on an older version you must immediately upgrade back to the newest version; that pattern is not documented. If your workaround involves downgrading just to get the import to succeed, then yes, once the import is done, the general guidance is to upgrade Airbyte again following the standard upgrade docs for your deployment method (e.g., Helm on K8s).[Upgrading Airbyte] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.