chore: bump patch versions to force registry update for supportLevel changes - #75645
Merged
Aaron ("AJ") Steers (aaronsteers) merged 1 commit intoMar 31, 2026
Conversation
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
|
Contributor
|
Contributor
|
Contributor
|
Contributor
|
…changes Uses bump_version_in_repo tool to properly update metadata.yaml, pyproject.toml, and docs changelog for all 5 connectors: - destination-motherduck: 0.2.2 → 0.2.3 (certified) - destination-pgvector: 0.1.8 → 0.1.9 (community) - destination-weaviate: 0.2.60 → 0.2.61 (community) - destination-milvus: 0.0.57 → 0.0.58 (community) - destination-snowflake-cortex: 0.2.27 → 0.2.28 (community)
devin-ai-integration
Bot
force-pushed
the
devin/1774926477-bump-versions-force-registry-update
branch
from
March 31, 2026 03:18
4619944 to
401b088
Compare
Contributor
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit 401b088. |
Aaron ("AJ") Steers (aaronsteers)
marked this pull request as ready for review
March 31, 2026 03:35
Aaron ("AJ") Steers (aaronsteers)
requested a review
from a team
as a code owner
March 31, 2026 03:35
Aaron ("AJ") Steers (aaronsteers)
merged commit Mar 31, 2026
c343b13
into
master
62 of 63 checks passed
Aaron ("AJ") Steers (aaronsteers)
deleted the
devin/1774926477-bump-versions-force-registry-update
branch
March 31, 2026 03:36
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
2 tasks
dilanalex
pushed a commit
to dilanalex/airbyte
that referenced
this pull request
Apr 6, 2026
…changes (airbytehq#75645) 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
Bumps patch versions for 5 destination connectors whose
supportLevelwas changed in #75299 and #75642 but whose registry entries were never updated. The previous PRs only modifiedsupportLevelwithout a version bump, and the publish pipeline does not resync per-connectorlatest/metadata in GCS unless the version changes — so the cloud registry still reflects the old classification.How
Patch version bump via the
bump_version_in_repoOps MCP tool, which updatesmetadata.yaml,pyproject.toml, and the docs changelog for each connector:No code changes. The version bump will cause the publish pipeline to rebuild and publish new Docker images (functionally identical) and, critically, resync the
latest/metadata to GCS so the registry compile picks up thesupportLevelchanges from the prior PRs.Review guide
Each connector has three files changed — verify version consistency between
metadata.yamlandpyproject.toml, and that the changelog entry indocs/is present:destination-milvus/metadata.yaml+pyproject.toml+docs/integrations/destinations/milvus.mddestination-motherduck/metadata.yaml+pyproject.toml+docs/integrations/destinations/motherduck.mddestination-pgvector/metadata.yaml+pyproject.toml+docs/integrations/destinations/pgvector.mddestination-snowflake-cortex/metadata.yaml+pyproject.toml+docs/integrations/destinations/snowflake-cortex.mddestination-weaviate/metadata.yaml+pyproject.toml+docs/integrations/destinations/weaviate.mdNote: This will trigger full connector image builds and publishes for all 5 connectors on merge.
Human review checklist
metadata.yaml(dockerImageTag) andpyproject.toml(version) for each connectorUser Impact
After merge and publish, the cloud registry will correctly reflect:
supportLevel: certified(promoted in chore: certify destination-motherduck #75642)supportLevel: community(demoted in chore: downgrade vector destinations fromcertifiedtocommunitysupport #75299)Users will see the corrected "Airbyte Connector" vs "Marketplace" classification in the Cloud UI connector catalog.
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)