Publish CalVer NuGet packages and GitHub releases from main

[cangelosilima]

Changes

Publish SyncSql.Grammar.PlSql and the SyncSql.Cli .NET tool independently after relevant changes reach main. Pull requests and manual runs validate packages only; tag pushes and other branches cannot publish.

Each main workflow generates a YYYY.M.D.BUILD CalVer version from the tested commit’s UTC date and the workflow run number, runs tests, packs the package, and publishes it to nuget.org through trusted publishing. It then creates a GitHub release with generated notes and the published .nupkg attached. The CLI also installs and smoke-tests its package before publication.

Generated tags point to the exact tested main commit. Reruns reuse the version and tag, skip an existing NuGet version, and recover incomplete draft releases or asset uploads. A conflicting tag is rejected rather than moved.

Enable the standalone grammar package with its ANTLR dependency, README, license, and notice; include its license/notice in the CLI package. Document account setup, automated releases, validation runs, and recovery. NUGET_USER and the two NuGet trusted-publishing policies are already configured.

Validation

• Actionlint passed for both workflows.
• All 10 release-automation tests passed, covering main-only guards, reruns, conflicting tags, API failures, and interrupted asset uploads.
• CalVer checks verified main versus validation versions and .NET assembly revision bounds.
• Both NuGet packages previously built and were inspected; the packed CLI installed and ran successfully.
• Repository pre-push checks run before the branch update, including .NET/site tests, coverage, and mutation gates.

Merging enables automatic publication for matching changes on main. This PR does not itself merge or publish a package.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-27T00:19:47.592585Z	f0f973c	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

Quality results

Quality gate: success
Commit: 84899448ea559f6ca58fa85ad0ec13e712cd3bb2 · View run and reports

Check	Result
Dependency vulnerabilities	success
CodeQL	success
CLI lint and format	success
CLI tests and coverage	success
CLI mutation (Core ≥90%, selected command files ≥55%)	success
CLI performance budgets	success
Site lint and format	success
Site tests and coverage	success
Site reachability mutation (100%)	success
Workflow lint	success
Coverage badge data	success

Line coverage	Measured	Minimum
CLI	100%	100%
Site	100%	80%

CLI line, branch, method, and full method coverage must each reach 100%. A missing report is shown as unavailable. See the linked run for test failures, detailed CLI/Site coverage summaries and HTML reports, and scanner results.