[Automated] Sync main after 1.2.1 release

[ballerina-bot]

Sync main after 1.2.1 release

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

This PR updates version references across configuration files for the CDC module. The main package version increments from 1.2.0 to 1.2.1 with matching updates to native dependencies. The Gradle project version advances to 1.2.2-SNAPSHOT, while several transitive dependencies are adjusted in Dependencies.toml.

Changes

Cohort / File(s)	Summary
Package Configuration ballerina/Ballerina.toml, ballerina/CompilerPlugin.toml	Package version bumped to 1.2.1 with corresponding updates to native (cdc-native-1.2.1.jar) and compiler-plugin (cdc-compiler-plugin-1.2.1.jar) artifact references.
Dependency Management ballerina/Dependencies.toml	Four public package versions adjusted: ballerinax/cdc upgraded to 1.2.1, while data.jsondata, observe, and ballerinax/java.jdbc downgraded to earlier patch versions.
Build Configuration gradle.properties	Project version advanced from 1.2.1-SNAPSHOT to 1.2.2-SNAPSHOT.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• [Automated] Sync main after 1.2.0 release #28: Updates the same versioned artifacts across Ballerina.toml, CompilerPlugin.toml, and gradle.properties for the CDC module release.

Suggested reviewers

• daneshk
• niveathika
• gayaldassanayake

Poem

🐰 Version bumps, a gentle hop,
From 1.2.0 to the new top,
Dependencies dance in harmony's way,
Gradle bounds forth with 1.2.2 today! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is vague and generic, consisting only of a single sentence that repeats the PR title without providing meaningful details about the changes or context.	Expand the description to include what was changed (version bumps, dependency updates), why the sync was necessary, and any verification steps taken.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the PR's primary purpose: syncing the main branch after the 1.2.1 release, which aligns with the actual changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-1.2.1

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.56%. Comparing base (f100cc4) to head (ef59b70).
⚠️ Report is 5 commits behind head on main.

❌ Your project status has failed because the head coverage (76.56%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff            @@
##               main      #30   +/-   ##
=========================================
  Coverage     76.56%   76.56%           
  Complexity      224      224           
=========================================
  Files            30       30           
  Lines          1084     1084           
  Branches        170      170           
=========================================
  Hits            830      830           
  Misses          176      176           
  Partials         78       78           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.