[Copilot]

The project had no canonical release log, which left the baseline release history opaque and made it harder for downstream consumers to track what shipped and what changed across versions.

• Summary

  • Add a root CHANGELOG.md in the standard Keep a Changelog format.
  • Define an Unreleased section for future changes and an initial 0.1.0 entry documenting the project’s first public baseline release.
  • Keep the release history aligned with the repository’s existing Maven versioning and expected release conventions.

• What changed

  • Added CHANGELOG.md at the repository root.
  • Structured it with the standard sections:
    • Unreleased
    • Added
    • Changed
    • Deprecated
    • Removed
    • Fixed
    • Security
  • Documented the initial 0.1.0 baseline release with a concise, consumer-facing overview of the project’s initial capabilities and layout.

• Release note scope

  • Captures the initial Java port of Microsoft ScriptDOM as the baseline release.
  • Notes the key modules and architecture: tsql-scriptdom-astgen and tsql-scriptdom-core.
  • Provides a stable place to track future additions and breaking changes without changing existing runtime behavior.

## [Unreleased]

### Added
- Changelog tracking for upcoming changes and release notes.

## [0.1.0] - 2026-10-11

### Added
- Initial public baseline release of the Java port of Microsoft ScriptDOM.

• Fixes Add CHANGELOG.md following Keep a Changelog standard #15

[Copilot]

Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.