@kapa.ai What should I do if a connector uses a deprecated API version. SHould I overwrite it or create a new one? This is happening with Greenhouse connector. See issue and PR.

Greenhouse Connector & Deprecated API — What to Do Based on the open issue and PR you linked, here's the situation and recommended path: Current Status The

source-greenhouse

connector (v0.7.28) uses the Greenhouse Harvest v1 API, which — along with v2 — is deprecated and will be removed on August 31, 2026. The new v3 API introduces OAuth authentication. [Greenhouse Issue] A community member has already submitted a PR (

source-greenhouse-harvest-v3

) as a new connector with OAuth support and 35+ streams. [Greenhouse v3 PR] Should You Overwrite or Create a New Connector? The general Airbyte guidance is to update the existing connector rather than create a new one, but since the v3 API introduces OAuth authentication (a breaking change in configuration), this is more nuanced: • Updating the existing connector is the preferred path when the changes can be made in a non-breaking way. If breaking changes are unavoidable, Airbyte requires a major version bump, a

breakingChanges

metadata entry, and a migration guide. [Breaking Changes Docs] • Creating a new connector (as done in the PR) is an alternative, but the Airbyte team has not yet confirmed which path they prefer for Greenhouse. The contributor who opened the PR explicitly asked for direction on whether to replace the existing connector or keep the new one. [Greenhouse Issue] Recommended Actions 1. If you're a user relying on

source-greenhouse

today: monitor the issue and be prepared to migrate before August 31, 2026. You can also use the community-contributed

source-greenhouse-harvest-v3

as a custom connector in the meantime. [Custom Connectors Docs] 2. If you want to contribute: comment on the open issue or the PR to get direction from the Airbyte team on whether to migrate the existing connector (with a major version bump) or proceed with the new connector approach. 3. If you're on Airbyte Cloud: open a support ticket referencing the issue URL to get prioritized attention. The Airbyte team has acknowledged the issue and escalated it internally, but no committed timeline has been given. [Greenhouse Issue] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.