chore(main): release 0.8.0 (#56)

* chore(main): release 0.8.0

* docs(changelog): rewrite v0.8.0 entries in prose style

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: Pawansingh3889

.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.7.0"
+  ".": "0.8.0"
 }

CHANGELOG.md

@@ -10,6 +10,10 @@ a deprecation window (see `GOVERNANCE.md` § Scope discipline).
 
 ## [Unreleased]
 
+## [0.8.0] - 2026-05-20
+
+Four new rules added since v0.7.0 (W021, E009, T006, W024) and a meaningful coverage fix to S001 `implicit-cross-join`. No breaking changes; existing pre-commit configs continue to work without modification.
+
 ### Added
 
 - **W021 `having-without-group-by`** - warns when `HAVING` appears
@@ -74,6 +78,10 @@ a deprecation window (see `GOVERNANCE.md` § Scope discipline).
   Snowflake/Postgres lateral join and not flagged. Resolves #41
   (the W027 comma-join request was a duplicate of S001).
 
+### Documentation
+
+- README and `action.yml` refresh for v0.7.0 (contracts pack, new contributors, missing rules) ([#38](https://github.com/Pawansingh3889/sql-guard/pull/38)).
+
 ## [0.7.0] - 2026-05-02
 
 Headline release: schema-aware linting via the new **Contracts pack**, three community-contributed rules (W014 / W015 / W022), and the `schema-snapshot` and `validate-contract` subcommands. Core registry is 43 rules (10 errors, 28 warnings, 5 Python-source). With `--contract` enabled the registry grows to 48 rules (12 errors, 31 warnings, 5 Python-source). Without `--contract` behaviour is identical to v0.6.x and there are no breaking changes.

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "sql-sop"
-version = "0.7.0"
+version = "0.8.0"
 description = "Fast rule-based SQL linter. Pre-commit hook + GitHub Action + CLI."
 readme = "README.md"
 license = "MIT"