feat: implement automated versioning with Release Please by Copilot · Pull Request #681

feat: implement automated versioning with Release Please by Copilot · Pull Request #681 · microsoft/go-sqlcmd

Add Release Please workflow and configuration for automated version management, changelog generation, and release creation based on conventional commits.

- Add .github/workflows/release-please.yml workflow
- Add release-please-config.json configuration
- Add .release-please-manifest.json for version tracking
- Create initial CHANGELOG.md
- Add CONTRIBUTING.md with release process documentation

Co-authored-by: dlevy-msft-sql <194277063+dlevy-msft-sql@users.noreply.github.com>

Add workflow to validate PR titles follow conventional commit format, ensuring automated version bumping works correctly with Release Please.

Co-authored-by: dlevy-msft-sql <194277063+dlevy-msft-sql@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Implement automated versioning with Release Please~~ feat: implement automated versioning with Release Please

Jan 31, 2026

Update comment to accurately reflect that requireScope: false makes scopes optional, not mandatory.

Co-authored-by: dlevy-msft-sql <194277063+dlevy-msft-sql@users.noreply.github.com>

Update workflow to use manifest command with explicit config and manifest files, enabling proper version tracking via .release-please-manifest.json as intended in the design.

Co-authored-by: dlevy-msft-sql <194277063+dlevy-msft-sql@users.noreply.github.com>

…tion

- Change to googleapis/release-please-action@v4.1.3 (google-github-actions version is deprecated)
- Add workflow_dispatch trigger for manual runs
- Update manifest version to 1.9.0 (current released version)
- Clarify in docs that git tag is created after Release PR merge, not during PR creation

Co-authored-by: dlevy-msft-sql <194277063+dlevy-msft-sql@users.noreply.github.com>