chore: certify destination-motherduck - #75642
Merged
Aaron ("AJ") Steers (aaronsteers) merged 1 commit intoMar 31, 2026
Merged
Conversation
Upgrade destination-motherduck from community to certified support level.
Contributor
🤖 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:
|
Contributor
👋 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
|
Contributor
|
Aaron ("AJ") Steers (aaronsteers)
marked this pull request as ready for review
March 31, 2026 02:14
Aaron ("AJ") Steers (aaronsteers)
requested a review
from a team
as a code owner
March 31, 2026 02:14
Comment on lines
39
to
41
| ab_internal: | ||
| sl: 100 | ||
| ql: 100 |
Member
Author
There was a problem hiding this comment.
Do we not need to update sl or ql?
Contributor
There was a problem hiding this comment.
Looking at existing certified destinations, sl and ql values vary widely — there's no single required value for certified status. Several certified destinations already use sl: 100, ql: 100:
destination-customer-io→ sl: 100, ql: 100destination-databricks→ sl: 100, ql: 100destination-hubspot→ sl: 100, ql: 100destination-mssql→ sl: 100, ql: 100destination-s3-data-lake→ sl: 100, ql: 100
Others use higher values (e.g. BigQuery, Snowflake, S3 use sl: 300, ql: 300).
So the current sl: 100, ql: 100 is compatible with certified status. Would you like me to bump these to a specific value, or leave as-is?
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Aaron ("AJ") Steers (aaronsteers)
merged commit Mar 31, 2026
d4a0815
into
master
58 of 59 checks passed
Aaron ("AJ") Steers (aaronsteers)
deleted the
devin/1774922954-certify-destination-motherduck
branch
March 31, 2026 02:16
3 tasks
dilanalex
pushed a commit
to dilanalex/airbyte
that referenced
this pull request
Apr 6, 2026
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Upgrades
destination-motherduckfromcommunitytocertifiedsupport level.How
Changed
supportLevel: community→supportLevel: certifiedin the connector'smetadata.yaml.Review guide
airbyte-integrations/connectors/destination-motherduck/metadata.yamlReviewer checks:
ab_internal.slandab_internal.qlfields are currently both100. Should these be increased (e.g. to200/300) to reflect certified status?releaseStageis stillalpha. Is this compatible withsupportLevel: certified, or should it be bumped tobeta/generally_available?remoteRegistries.pypi.enabledisfalse. Confirm this is acceptable for a certified connector.User Impact
destination-motherduckwill appear as "certified" instead of "community" in the Airbyte UI and connector registry. No functional changes.Can this PR be safely reverted and rolled back?
Link to Devin session: https://app.devin.ai/sessions/0d4c25fa273147bba0ed9ed9d4f76a0b
Requested by: Aaron ("AJ") Steers (@aaronsteers)