Destination Dev Null: test release; pin to CDK artifact

[edgao]

noop release just to test some new publish workflow stuff

also firing a prerelease here https://github.com/airbytehq/airbyte/actions/runs/16913838696. Validated that its metadata got uploaded to the dev bucket identically as airbyte-ci's real upload:

diff <(gsutil cat gs://io-airbyte-cloud-spec-cache/specs/airbyte/destination-dev-null/0.8.2-dev.e6b32cbfcf/spec.json | jq) <(gsutil cat gs://dev-airbyte-cloud-connector-metadata-service/specs/airbyte/destination-dev-null/0.8.2-dev.e6b32cbfcf/spec.json | jq)
diff <(gsutil cat gs://io-airbyte-cloud-spec-cache/specs/airbyte/destination-dev-null/0.8.2-dev.e6b32cbfcf/spec.cloud.json | jq) <(gsutil cat gs://dev-airbyte-cloud-connector-metadata-service/specs/airbyte/destination-dev-null/0.8.2-dev.e6b32cbfcf/spec.cloud.json | jq)
diff <(gsutil cat gs://prod-airbyte-cloud-connector-metadata-service/sbom/airbyte/destination-dev-null/0.8.2-dev.e6b32cbfcf.spdx.json | jq) <(gsutil cat gs://dev-airbyte-cloud-connector-metadata-service/sbom/airbyte/destination-dev-null/0.8.2-dev.e6b32cbfcf.spdx.json | jq)
diff <(gsutil cat gs://prod-airbyte-cloud-connector-metadata-service/metadata/airbyte/destination-dev-null/0.8.2-dev.e6b32cbfcf/doc.md) <(gsutil cat gs://dev-airbyte-cloud-connector-metadata-service/metadata/airbyte/destination-dev-null/0.8.2-dev.e6b32cbfcf/doc.md)
diff <(gsutil cat gs://prod-airbyte-cloud-connector-metadata-service/metadata/airbyte/destination-dev-null/0.8.2-dev.e6b32cbfcf/metadata.yaml) <(gsutil cat gs://dev-airbyte-cloud-connector-metadata-service/metadata/airbyte/destination-dev-null/0.8.2-dev.e6b32cbfcf/metadata.yaml)

Important

Auto-merge enabled.

This PR is set to merge automatically when all requirements are met.

Note

Auto-merge may have been disabled. Please check the PR status to confirm.

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

Helpful Resources

• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Live Tests
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

PR Slash Commands

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

• /format-fix - Fixes most formatting issues.
• /bump-version - Bumps connector versions.
  • You can specify a custom changelog by passing changelog. Example: /bump-version changelog="My cool update"
  • Leaving the changelog arg blank will auto-populate the changelog from the PR title.
• /run-cat-tests - Runs legacy CAT tests (Connector Acceptance Tests)
• /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
• /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.

📝 Edit this welcome message.

[github-actions]

destination-dev-null Connector Test Results

47 tests   15 ✅  39s ⏱️
 4 suites  32 💤
 4 files     0 ❌

Results for commit 9e38519.

♻️ This comment has been updated with latest results.

[github-actions]

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-duglh0vfs-airbyte-growth.vercel.app

Built with commit 9e38519.
This pull request is being automatically deployed with vercel-action

[frifriSF59]

Should we use this PR to pin the destination to the latest version of the CDK?

[edgao]

lol. I definitely thought we'd already done that. Lemme check with the speed folks if they care, otherwise yes.