Repository navigation
chore(connectors): roll Cloud back to pre-SDM-7.23.7 versions for 19 sources - #83183
Conversation
…sources Co-Authored-By: syed.khadeer@airbyte.io <cloud-support@airbyte.io>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
|
Note Autopilot progressive rollouts are not enabled for the following modified connector(s):
This is a courtesy heads-up only — it does not block merge or fail any check. |
|
|
|
Re Daryna Ishchenko (@darynaishchenko)'s request to drop any connector here that doesn't use custom components: I re-verified all 19 and none can be dropped — every one of them bundles a
Worth noting the gate is not limited to Verification of the fix on a real Cloud connection (Devin sandbox workspace, dummy Chargebee credentials, Dev Null destination):
|
|
|
|
|
|
/force-merge reason="version rollback for sources affected by cdk update"
|
What
Requested by Daryna Ishchenko (@darynaishchenko) as a fleet-wide alternative to per-customer version pins.
19 published sources are currently broken in Cloud because they are built on
source-declarative-manifest:7.23.7, which requiresAIRBYTE_ENABLE_UNSAFE_CODE=truefor anyCustom*component — including components bundled inside the connector's own published image. Cloud does not set that variable, socheck,discoverandreadall fail immediately withAirbyteCustomCodeNotPermittedError.Root cause and permanent fix: airbytehq/airbyte-python-cdk#1082 / airbytehq/airbyte-python-cdk#1083.
This PR rolls the Cloud registry back to each connector's last version built on SDM 7.23.6 (7.23.5 for
source-klaviyo) using theregistryOverrides.cloud.dockerImageTagmetadata field, so affected customers recover without an admin applying an actor-level pin one workspace at a time.How
Per connector: patch version bump (required for the metadata change to be published) plus a Cloud registry override, e.g.
Cloud rollback targets:
Target versions were derived by walking each connector's published registry metadata backwards until
connectorBuildOptions.baseImagewas no longer7.23.7.Review guide
airbyte-integrations/connectors/*/metadata.yaml— two-line change each; no manifest, spec or component changes.docs/integrations/sources/*.md— changelog rows.Note deliberately not done here: the new versions still declare
baseImage: 7.23.7, so OSS/Self-Managed users continue to receive a broken image unless they setAIRBYTE_ENABLE_UNSAFE_CODE=true. RevertingbaseImageto the 7.23.6 digest instead would cover OSS too, at the cost of 19 real rebuilds. Happy to switch this PR to that shape if preferred.User Impact
Affected Cloud customers stop failing without any per-workspace intervention, at the cost of missing the newest connector patch until airbytehq/airbyte-python-cdk#1083 ships and the connectors are rebuilt on a fixed base image. At that point the
registryOverrides.cloud.dockerImageTaglines must be removed again — this is a temporary rollback, not a permanent state.Can this PR be safely reverted and rolled back?
Link to Devin session: https://app.devin.ai/sessions/fbef868f12844f26b7cb6edbc1b3a8b0
Requested by: Airbyte Support (@Airbyte-Support)