fix: replace deprecated ObjectNode.fields usage in source-mysql

[Constantine Kim 김현진 (elegantcoder)]

What

Replace deprecated Jackson ObjectNode.fields() usage in source-mysql with properties(), and bump the connector's pinned Bulk CDK version from 0.1.77 to 0.2.8.

The deprecated Jackson call was the immediate CI failure, but while reproducing it we also found that source-mysql no longer compiles cleanly against the stale published Bulk CDK pin on master. Updating the pin to the current published 0.2.8 artifact restores the connector classpath and keeps the connector green.

Related context:

• Bulk CDK Debezium bump PR: fix: bump bulk extract CDK Debezium to 3.4.2.Final #75528
• Airbyte discussion with the same MySQL CDC failure mode: CDC Replication Error: MySqlDbSet.getUUID() NullPointerException #74305

How

• Update MySqlSourceDebeziumOperations.deserializeStateUnvalidated() to iterate with ObjectNode.properties() instead of the deprecated fields() API
• Bump source-mysql's pinned Bulk CDK version from 0.1.77 to 0.2.8
• Keep the connector metadata version at 3.51.6
• Update the MySQL connector changelog entry to describe both changes

Review guide

1. airbyte-integrations/connectors/source-mysql/src/main/kotlin/io/airbyte/integrations/source/mysql/MySqlSourceDebeziumOperations.kt
2. airbyte-integrations/connectors/source-mysql/gradle.properties
3. airbyte-integrations/connectors/source-mysql/metadata.yaml
4. docs/integrations/sources/mysql.md

User Impact

This avoids connector compatibility failures caused by deprecated Jackson APIs being treated as errors, and updates source-mysql to a published Bulk CDK version that matches the current connector sources. There are no source config changes expected for users.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

[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]

👋 Welcome to Airbyte!

Thank you for your contribution from elegantcoder/airbyte! We're excited to have you in the Airbyte community.

If you have any questions, feel free to ask in the PR comments or join our Slack community.

💡 Show Tips and Tricks

PR Slash Commands

As needed or by request, Airbyte Maintainers can execute the following slash commands on your PR:

• /format-fix - Fixes most formatting issues.
• /bump-version - Bumps connector versions.
• /run-connector-tests - Runs connector tests.
• /run-cat-tests - Runs CAT tests.
• /run-regression-tests - Runs regression tests for the modified connector(s).
• /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
• /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
• /ai-review - AI-powered PR review for connector safety and quality gates.
• /force-merge reason="<A_GOOD_REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.

Tips for Working with CI

1. Pre-Release Checks. Please pay attention to these, as they contain standard checks on the metadata.yaml file, docs requirements, etc. If you need help resolving a pre-release check, please ask a maintainer.
   • Note: If you are creating a new connector, please be sure to replace the default logo.svg file with a suitable icon.
2. Connector CI Tests. Some failures here may be expected if your tests require credentials. Please review these results to ensure (1) unit tests are passing, if applicable, and (2) integration tests pass to the degree possible and expected.
3. (Optional.) BYO Connector Credentials for tests in your fork. You can optionally set up your fork with BYO credentials for your connector. This can significantly speed up your review, ensuring your changes are fully tested before the maintainers begin their review.

📚 Show Repo Guidance

Helpful Resources

• Maintainers: AI-SDLC Docs (internal link)
• PR Guidelines: Check our guidelines for contributions.
• Breaking Changes Guide: Guide to breaking changes, migration guides, and upgrade deadlines.
• Developing Connectors Locally: Learn how to set up your environment and develop connectors locally.
• If you enable BYO Connector Credentials within your fork, you can view your test results here:
  

📝 Edit this welcome message.

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}