Bump the version to 1.3.0

[Nuvindu]

Purpose

This PR will add the following updates.

• Bump the version to 1.3.0.
• Add the changelog

Version Release 1.3.0

This pull request prepares the project for the 1.3.0 release by updating version metadata and adding release documentation.

Changes

• Version bumps:
  • gradle.properties: version -> 1.3.0-SNAPSHOT
  • module-ballerina-xsd/Ballerina.toml: package version -> "1.3.0"
  • module-ballerina-xsd/Dependencies.toml: xsdtool package version -> "1.3.0"
  • module-ballerina-xsd/BalTool.toml: references updated to xsd-cli and xsd-core 1.3.0-SNAPSHOT
  • build-config/resources/* files updated to align with version 1.3.0
• Documentation:
  • Added/updated changelog.md with an Unreleased section (items for 1.3.0) and historical release notes (1.2.0, 1.1.2, 1.1.1, 1.1.0, 1.0.8).

Impact

• These are configuration and documentation updates to prepare the 1.3.0 release; no source code logic or exported/public API declarations were modified.

[coderabbitai]

📝 Walkthrough

Walkthrough

This change updates project version references from 1.2.1 to 1.3.0 (including SNAPSHOT variants) in root and module configuration files and adds a detailed changelog.md with an Unreleased section and historical release notes. No source code or exported/public declarations were modified.

Changes

Cohort / File(s)	Summary
Changelog Documentation changelog.md	Added an Unreleased section with Added/Fixed entries and expanded historical release notes (1.2.0, 1.1.2, 1.1.1, 1.1.0, 1.0.8). Documentation-only changes.
Root Version Property gradle.properties	Bumped project version from 1.2.1-SNAPSHOT to 1.3.0-SNAPSHOT.
Module Package Version module-ballerina-xsd/Ballerina.toml	Updated package version from "1.2.1" to "1.3.0".
Module Dependency Versions module-ballerina-xsd/Dependencies.toml, module-ballerina-xsd/BalTool.toml	Updated xsdtool/xsd-cli/xsd-core dependency versions from 1.2.1/1.2.1-SNAPSHOT to 1.3.0/1.3.0-SNAPSHOT.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 From one-dot-two-one we hop to one-dot-three,
Notes in the changelog singing happily,
Version bumps lined up in a row,
Docs refreshed with history's glow,
I nibble a carrot and cheer: "Release time!" 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete and missing most required template sections. It only addresses Purpose with minimal detail and does not include Goals, Approach, User stories, Release notes, Documentation, Training, Certification, Marketing, Tests, Security checks, Samples, Related PRs, Migrations, Test environment, or Learning sections.	Fill out the description template with relevant sections for this version bump release, including at least Goals, Approach, Release notes, and Documentation impact; mark N/A for sections that don't apply with brief explanations.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: bumping the project version to 1.3.0, which is reflected in multiple configuration files (gradle.properties, Ballerina.toml, BalTool.toml, Dependencies.toml) and the changelog.
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

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

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

Inline comments:
In `@changelog.md`:
- Around line 40-41: Replace the phrase "floating point" in the changelog entry
with the hyphenated form "floating-point" to match style; locate the entry that
reads "Support converting all floating point values" and update it to "Support
converting all floating-point values".

[coderabbitai]

🧹 Nitpick comments (1)

changelog.md (1)

9-20: Consider adding PR links consistently across all entries.

Some entries in the Unreleased section include PR links (lines 11, 16) while others do not (lines 12, 17-20). If these changes have associated PRs, adding links would improve traceability.

🤖 Prompt for AI Agents

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

In `@changelog.md` around lines 9 - 20, The Unreleased changelog entries mix
linked and unlinked PRs; update the bullets so all entries consistently include
PR links where available. For each bullet text (e.g., "Add element annotation to
record fields", "Set the maximum maxOccurs value to 65535", "Support NMTOKENS as
built-in type", "Fix optional field generation for sequence groups", "Handle
ambiguity when a single element inside a sequence", "Fix setting attributes and
content fields optional", "Set sequenceGroup optional when all child elements
are optional") add the corresponding GitHub PR URL in the same format used
elsewhere (square-bracketed title linking to the PR) or explicitly mark entries
without PRs (e.g., add "(no PR)" or similar) to make traceability consistent.
Ensure formatting matches the existing markdown style.

🤖 Prompt for all review comments with AI agents

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

Nitpick comments:
In `@changelog.md`:
- Around line 9-20: The Unreleased changelog entries mix linked and unlinked
PRs; update the bullets so all entries consistently include PR links where
available. For each bullet text (e.g., "Add element annotation to record
fields", "Set the maximum maxOccurs value to 65535", "Support NMTOKENS as
built-in type", "Fix optional field generation for sequence groups", "Handle
ambiguity when a single element inside a sequence", "Fix setting attributes and
content fields optional", "Set sequenceGroup optional when all child elements
are optional") add the corresponding GitHub PR URL in the same format used
elsewhere (square-bracketed title linking to the PR) or explicitly mark entries
without PRs (e.g., add "(no PR)" or similar) to make traceability consistent.
Ensure formatting matches the existing markdown style.