[octavia-bot]

Automated sync of main into release-candidate/v1 could not fast-forward or merge cleanly.

release-candidate/v1 is 1 commit(s) behind main. Please resolve the merge conflicts on auto-sync/release-candidate-v1/from-main-c3e13c83 and merge this PR.

This PR's branch is refreshed from main on each run until you push conflict-resolution commits to it; after that it is left untouched so your work is preserved.

Workflow run: https://github.com/airbytehq/PyAirbyte/actions/runs/40367277806

[octavia-bot]

Note

📝 PR Converted to Draft

More info...

Thank you for creating this PR. As a policy to protect our engineers' time, Airbyte requires all PRs to be created first in draft status. Your PR has been automatically converted to draft status in respect for this policy.

As soon as your PR is ready for formal review, you can proceed to convert the PR to "ready for review" status by clicking the "Ready for review" button at the bottom of the PR page.

To skip draft status in future PRs, please include [ready] in your PR title or add the skip-draft-status label when creating your PR.

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

Testing This PyAirbyte Version

You can test this version of PyAirbyte using the following:

# Run PyAirbyte CLI from this branch:
uvx --from 'git+https://github.com/airbytehq/PyAirbyte.git@auto-sync/release-candidate-v1/from-main-c3e13c83' pyairbyte --help

# Install PyAirbyte from this branch for development:
pip install 'git+https://github.com/airbytehq/PyAirbyte.git@auto-sync/release-candidate-v1/from-main-c3e13c83'

PR Slash Commands

Airbyte Maintainers can execute the following slash commands on your PR:

• /fix-pr - Fixes most formatting and linting issues
• /uv-lock - Updates uv.lock file
• /test-pr - Runs tests with the updated PyAirbyte
• /prerelease - Builds and publishes a prerelease version to PyPI
• /evals - Runs the Cloud MCP evals that use the MCP tools this PR changed (/evals full=true runs the full suite)

📚 Show Repo Guidance

Helpful Resources

• PyAirbyte Documentation
• API Reference

Community Support

Questions? Join the #pyairbyte channel in our Slack workspace.

📝 Edit this welcome message.

[Copilot]

🟢 Approval recommended

The changes are localized, preserve deployment behavior, and include regression coverage with no unresolved findings.

No open issues 🎉

What changed in this PR

This sync PR brings a focused update to the release-candidate branch’s No-op destination deployment tool, clarifying its parameter names and MCP schema descriptions.

Changes:

• Rename the tool’s name parameter to destination_name while preserving deployment defaults.
• Add descriptions for the destination name and uniqueness parameters.
• Add regression tests for explicit and default arguments and parameter descriptions.

File	Description
tests/​unit_tests/​test_mcp_cloud.py	Adds coverage for deployment arguments, defaults, and schema descriptions.
airbyte/​mcp/​cloud.py	Renames the destination-name parameter and adds schema metadata.

_{Review effort: Balanced}

[github-code-quality]

Code coverage overview

Languages: Python

Python / code-coverage/pytest-unit

release-candidate/v1	auto-sync/release-ca... 120babb	+/-
—	77%	—

Line coverage data for the release-candidate/v1 branch is not yet available.

View coverage of the 10 most covered files.

File	release-candidate/v1	auto-sync/release-ca... 120babb	+/-
airbyte/cloud/models.py	—	97%	—
airbyte/mcp/_sso_auth.py	—	96%	—
airbyte/_direct...ctors/models.py	—	95%	—
airbyte/cloud/client.py	—	90%	—
airbyte/exceptions.py	—	90%	—
airbyte/mcp/cloud.py	—	85%	—
airbyte/progress.py	—	80%	—
airbyte/cloud/connectors.py	—	79%	—
airbyte/shared/...ql_processor.py	—	68%	—
airbyte/_util/api_util.py	—	67%	—

ℹ️ Calculations represent line coverage. Results may change as calculations are updated.