[Automated] Sync main after 1.2.0 release

[ballerina-bot]

Sync main after 1.2.0 release

Summary

This pull request syncs the main branch following the completion of the 1.2.0 release. The changes consist of version updates across configuration files to reflect the finalized release build.

Changes

Build Configuration Updates:

• Updated ballerina/Ballerina.toml to reference the finalized 1.2.0 release artifacts for the io.ballerina.lib.cdc dependency, replacing snapshot versions with stable release versions
• Updated ballerina/CompilerPlugin.toml to reference the finalized 1.2.0 release compiler plugin artifact
• Bumped gradle.properties to version 1.2.1-SNAPSHOT to prepare for the next development cycle

These changes finalize the transition from the 1.2.0 release branch to the main development line with updated artifact references and incremented version numbers for ongoing development.

[coderabbitai]

📝 Walkthrough

Walkthrough

Release preparation changes that convert SNAPSHOT dependencies to stable 1.2.0 versions while bumping the project version to 1.2.1-SNAPSHOT for continued development.

Changes

Cohort / File(s)	Summary
Dependency Version Updates ballerina/Ballerina.toml, ballerina/CompilerPlugin.toml	Updated CDC native and compiler plugin dependencies from SNAPSHOT (1.2.0-SNAPSHOT) to release version (1.2.0), including artifact ID and path adjustments.
Project Version Bump gradle.properties	Incremented project version from 1.2.0-SNAPSHOT to 1.2.1-SNAPSHOT.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• daneshk
• niveathika

Poem

🐰 From snapshots to releases, we hop along the way,
A version dance of 1.2.0, then 1.2.1 to stay,
The gradle bounds forward, dependencies aligned,
A stable build awaits, with futures yet to find! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is minimal and lacks required template sections like Purpose, Fixes, Examples, and the completion checklist specified in the repository template.	Expand the description to follow the repository template by adding Purpose, Fixes sections, and completing the checklist items to document the release synchronization changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main purpose: syncing main branch after the 1.2.0 release, which matches the version updates in the 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.0

---

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

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

ballerina/Ballerina.toml (1)

4-4: ⚠️ Potential issue | 🔴 Critical

Regenerate TOML files from templates using the build system.

The package version and native artifact references in ballerina/Ballerina.toml are stale. Since gradle.properties was bumped to 1.2.1-SNAPSHOT, the TOML files must be regenerated via the updateTomlFiles Gradle task to reflect this change. The template substitution will produce:

• Line 4: version = "1.2.1" (stripped SNAPSHOT)
• Lines 18-20: Native artifact paths with 1.2.1-SNAPSHOT to match the native build output

Running the build will regenerate these files correctly; manually editing them to hardcoded SNAPSHOT versions is not the intended pattern for this project, as these files are generated from build-config/resources/Ballerina.toml templates.

Also applies to: 18-20

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@ballerina/Ballerina.toml` at line 4, The Ballerina.toml file is stale — do
not edit it manually; run the Gradle task that regenerates TOML templates
(updateTomlFiles) so the template in build-config/resources/Ballerina.toml
substitutes the new version and native artifact paths; this will change the
version line from "1.2.0" to "1.2.1" (stripping -SNAPSHOT) and update the native
artifact references (lines around 18–20) to include "1.2.1-SNAPSHOT" as produced
by the build output.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@ballerina/Ballerina.toml`:
- Line 4: The Ballerina.toml file is stale — do not edit it manually; run the
Gradle task that regenerates TOML templates (updateTomlFiles) so the template in
build-config/resources/Ballerina.toml substitutes the new version and native
artifact paths; this will change the version line from "1.2.0" to "1.2.1"
(stripping -SNAPSHOT) and update the native artifact references (lines around
18–20) to include "1.2.1-SNAPSHOT" as produced by the build output.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.56%. Comparing base (c241584) to head (240c343).
⚠️ Report is 4 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      #28   +/-   ##
=========================================
  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.