@kapa.ai May i know when did

appVersion

changed to

2.0.1-alpha-7e24df1

instead of

2.0.1

?

The knowledge sources do not contain any information about an

appVersion

value of

2.0.1-alpha-7e24df1

or when such a change may have occurred. The sources only reference

appVersion

values like

2.0.0

,

2.0.1

,

1.8.5

, etc., in the context of Helm chart versions. I'm unable to provide a confident answer about this specific alpha/commit-tagged version based on the available information. I'd recommend checking the official Airbyte Helm chart repository or release notes directly for details on that specific version tag. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai can you check and confirm, please

Based on the knowledge sources available to me, I can confirm my previous answer: there is no information about an

appVersion

of

2.0.1-alpha-7e24df1

in any of the provided documents. The only

appVersion

values referenced in the knowledge sources are standard release versions, such as: [Airbyte Helm chart versions] The knowledge sources do not contain any information about alpha or commit-tagged

appVersion

values like

2.0.1-alpha-7e24df1

. For accurate details on that specific version, I'd recommend checking the Airbyte GitHub repository or the Helm chart release history directly. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements

@kapa.ai What caused all components to suddenly use the unavailable image version

2.0.1-alpha-7e24df1

, leading to the failure of all connection syncs?

The knowledge sources do not contain any information about the specific image version

2.0.1-alpha-7e24df1

or what caused components to switch to it. However, the knowledge sources do document a related pattern of issues where Airbyte Helm chart releases referenced Docker image tags that were not properly published to Docker Hub. For example: • The

airbyte/utils:2.0.1

and

airbyte/async-profiler:2.0.1

images were missing from Docker Hub even though the Helm chart referenced them. [missing images issue] • Similarly,

airbyte/webapp:1.7.2

was not published due to an issue in the release workflow. [webapp image issue] • There was also a known bug where connector prerelease publish pipelines produced malformed Docker image tags (e.g.,

2.23.15-rc.2-preview.998ce3c

instead of

2.23.15-preview.998ce3c

) due to multiple independent code paths naively concatenating version suffixes without stripping existing pre-release suffixes. [publish pipeline fix] The alpha/commit-tagged format

2.0.1-alpha-7e24df1

is consistent with the kind of malformed tags described in that bug. However, I cannot confirm this is the exact cause of your issue based solely on the available knowledge sources. I'd recommend: 1. Checking the Airbyte GitHub Issues for your specific version. 2. Joining the Airbyte Community Slack for peer support. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai https://airbytehq.github.io/helm-charts/index.yaml I can see

appVersion: 2.0.2-alpha-c905e75
    created: "2026-03-26T00:08:53.984085451Z"

The knowledge sources available to me do not contain any information about the

appVersion: 2.0.2-alpha-c905e75

entry from the Helm chart index, nor details about why alpha/commit-tagged versions like this appear in the chart index. The URL you've referenced (

https://airbytehq.github.io/helm-charts/index.yaml

) is not part of the knowledge sources I have access to, so I cannot analyze or confirm its contents. Based strictly on what the knowledge sources do tell us, there have been recurring issues with Airbyte Helm chart releases where published chart versions referenced Docker images that either didn't exist or had unexpected tags. [missing images issue] [Helm chart issues] However, I cannot make any specific claims about the

2.0.2-alpha-c905e75

version or what caused it to appear. For accurate and up-to-date information, I'd recommend: 1. Checking the Airbyte GitHub repository directly for related issues. 2. Joining the Airbyte Community Slack to ask the platform team directly. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.