ci: replace snap install yq with direct binary download

[Alfredo Garcia (agarctfi)]

What

The snap store has been unreachable from GitHub Actions runners all day, causing all connector pre-release publish workflows to fail with:

error: unable to contact snap store

Affected connectors today (8+ failed runs):

• source-google-ads (PR fix(source-google-ads): mount TimeoutHTTPAdapter on parent-stream sessions (4.2.6-rc.2) #77663) — 4 failures
• source-airtable (PR feat(source-airtable): add oauth_connector_input_specification with granular scopes #76071)
• source-snapchat-marketing (PR feat(source-snapchat-marketing): add oauthConnectorInputSpecification with scopes array #76214)
• source-linear (PR feat(source-linear): add OAuth 2.0 support #77578)
• source-microsoft-dataverse (PR feat(source-microsoft-dataverse)!: map DateOnly fields to date format instead of date-time #77565)

Requested by Alfredo Garcia (@agarctfi).

How

Replace sudo snap install yq with a direct binary download from the mikefarah/yq GitHub releases in all 5 occurrences:

1. .github/actions/connector-image-build-push/action.yml — used by the publish workflow
2. .github/workflows/auto-upgrade-certified-connectors-cdk.yml (2 occurrences)
3. .github/workflows/cdk-source-connector-compatibility-test.yml
4. .github/workflows/cdk-destination-connector-compatibility-test.yml

The new install method (wget from GitHub releases) does not depend on the snap store and is a common pattern for installing yq in CI.

Review guide

1. .github/actions/connector-image-build-push/action.yml — line 83
2. .github/workflows/auto-upgrade-certified-connectors-cdk.yml — lines 29, 73
3. .github/workflows/cdk-source-connector-compatibility-test.yml — line 25
4. .github/workflows/cdk-destination-connector-compatibility-test.yml — line 25

User Impact

Unblocks all connector pre-release publish workflows that are currently failing due to the snap store outage.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

---

Devin session

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

• 🛠️ Quick Fixes
  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
    • Bump types: patch (default), minor, major, major_rc, rc, promote.
    • The rc type is a smart default: applies minor_rc if stable, or bumps the RC number if already RC.
    • The promote type strips the RC suffix to finalize a release.
    • Example: /bump-version type=rc or /bump-version type=minor
  • /bump-progressive-rollout-version - Alias for /bump-version type=rc. Bumps with an RC suffix and enables progressive rollout.
• ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
  • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
  • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
  • /ai-review - AI-powered PR review for connector safety and quality gates.
• 📝 AI Documentation:
  • /ai-docs-review - AI-powered documentation review for PRs with connector changes.
  • /ai-create-docs-pr - Creates a documentation PR for connector changes, stacked on the current PR.
• 🚀 Connector Releases:
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
• ☕️ JVM connectors:
  • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
    Example: /update-connector-cdk-version connector=destination-bigquery
• 🐍 Python connectors:
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
• ⚙️ Admin commands:
  • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
    Example: /force-merge reason="CI is flaky, tests pass locally"

📚 Show Repo Guidance

Helpful Resources

• Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

📝 Edit this welcome message.