Release 1.1.0

Release 1.1

Date: 2026-09-21

OmniSQL 1.1 introduces the O(1) Memory Streaming Architecture, enabling the linter to parse and validate multi-gigabyte warehouse dumps with a constant, minimal memory footprint. It also ships with robust regex pre-processing and native Snowflake dialect support.

🚀 Features

• O(1) Memory Streaming Architecture: Completely overhauled the core parsing engine to use a byte-by-byte StreamingSqlReader. This allows OmniSQL to lint massive data dumps (e.g., 4GB+) without hitting OS memory limits, scaling linearly with disk I/O.
• On-the-Fly Data Bypassing: The streaming reader now instantly fast-forwards through massive COPY ... FROM stdin; data payloads and drops unsupported DDL statements before they reach the AST parser, saving gigabytes of memory.
• Style Auto-Fixer Heuristics: Added a file-size safeguard that automatically disables the style auto-fixer (--fix) for files larger than 100MB to prevent excessive memory buffering.
• Snowflake Dialect Support: Implemented a regex pre-processor and extended the CLI to accept --dialect snowflake, enabling native linting for Snowflake-specific SQL syntax and JSON path traversal syntax.

📝 Documentation

• Dialect CLI Usage: Added documentation to all distribution READMEs detailing how to explicitly set the SQL dialect (e.g., --dialect snowflake).
• Implementation Plan Sync: Reorganized documentation into the docs/ folder, added it to .gitignore to keep the root clean, and updated CONTRIBUTING.md to reflect these changes.

🛠️ Maintenance & Chores

• Regex Pre-Processor Fixes: Merged PR #15 to correctly intercept and strip out raw data blocks and unparseable PostgreSQL DDLs, preserving exact line numbers for accurate lint reporting.

---

Thank you to everyone who contributed to this release!

What's Changed

• feat: regex pre-processor and Snowflake dialect support by @Shivam-Jha96 in #15
• feat: O(1) Memory Streaming Architecture & Repo Documentation Sync by @Shivam-Jha96 in #16

Full Changelog: v1.0.6...v1.1.0

Release 1.0.6

Release 1.0.6

Date: 2026-09-20

OmniSQL 1.0.6 introduces critical documentation enhancements for our auto-fix engine and schema integrations, ensuring users understand the current boundaries of the semantic checking engine.

📝 Documentation

• Schema & dbt Manifest Examples: Added explicit command-line examples across all READMEs demonstrating how to lint SQL files using local DDL schemas (--schema) or dbt configurations (--dbt-manifest).
• Auto-Fix Disclaimer: Added explicit --fix examples alongside schema validation, supplemented with an important disclaimer clarifying that OmniSQL's auto-fix engine currently handles stylistic violations (casing, commas) but does not automatically modify semantic or security errors.

🛠️ Maintenance & Chores

• Version Bumps: Incremented versions to 1.0.6 across Cargo.toml, Node environments, and PyPI scripts to trigger a fresh CI/CD rollout.

---

Thank you to everyone who contributed to this release!

Full Changelog: v1.0.5...v1.0.6

Release 1.0.5

Release 1.0.5

Date: 2026-09-20

OmniSQL 1.0.5 introduces dynamic versioning for our NPM and PyPI wrappers, live-updating repository badges, and a new verbose runtime logging system for the CLI.

🚀 Features

• Verbose Runtime Logs: Implemented detailed runtime debug logs directly in the CLI engine. Users can now opt-in for deeper insights during linting.
• Instant Version Reporting: The -V and --version flags now intercept commands instantaneously inside the JS and Python wrappers to print correct versions without invoking the underlying Rust binary.

🐛 Bug Fixes

• Dynamic Installer Resolution: Fixed an issue where Node and Python package installations could cache or point to outdated omnisql native binaries. Installation scripts now correctly read their dynamic package versions directly from package.json and importlib.metadata.

📝 Documentation

• Usage Guides & Upgrade Commands: Overhauled all README files across the repository, VS Code marketplace, and PyPI to include explicit CLI linting guides, auto-fix instructions, and package update commands.
• Dynamic Version Badges: Replaced statically hardcoded v1.0.0 references in the documentation with live-updating version badges for NPM, PyPI, and the VS Code Marketplace.
• Implementation Plan Sync: Kept living documentation completely up to date with recent structural completions (Phases 11-13).

🛠️ Maintenance & Chores

• Repository Sanitization: Cleaned up dummy files, corrected .gitignore rules for temporary target directories, and relocated scratch files to keep the core repository pristine.
• Version Bumps: Bumped across Cargo.toml, npm/package.json, python/setup.py, and vscode-extension/package.json to prepare for 1.0.5 deployment.

---

Thank you to everyone who contributed to this release!

Full Changelog: v1.0.4...v1.0.5

Release 1.0.4

Release 1.0.4

Date: 2026-09-20

OmniSQL 1.0.4 introduces dynamic versioning for our NPM and PyPI wrappers, live-updating repository badges, and a new verbose runtime logging system for the CLI.

🚀 Features

• Verbose Runtime Logs: Implemented detailed runtime debug logs directly in the CLI engine. Users can now opt-in for deeper insights during linting.
• Instant Version Reporting: The -V and --version flags now intercept commands instantaneously inside the JS and Python wrappers to print correct versions without invoking the underlying Rust binary.

🐛 Bug Fixes

• Dynamic Installer Resolution: Fixed an issue where Node and Python package installations could cache or point to outdated omnisql native binaries. Installation scripts now correctly read their dynamic package versions directly from package.json and importlib.metadata.

📝 Documentation

• Usage Guides & Upgrade Commands: Overhauled all README files across the repository, VS Code marketplace, and PyPI to include explicit CLI linting guides, auto-fix instructions, and package update commands.
• Dynamic Version Badges: Replaced statically hardcoded v1.0.0 references in the documentation with live-updating version badges for NPM, PyPI, and the VS Code Marketplace.
• Implementation Plan Sync: Kept living documentation completely up to date with recent structural completions (Phases 11-13).

🛠️ Maintenance & Chores

• Repository Sanitization: Cleaned up dummy files, corrected .gitignore rules for temporary target directories, and relocated scratch files to keep the core repository pristine.
• Version Bumps: Bumped across Cargo.toml, npm/package.json, python/setup.py, and vscode-extension/package.json to prepare for 1.0.4 deployment.

---

Thank you to everyone who contributed to this release!

What's Changed

• CLI Runtime Debug Logs & Repository Sanitization by @Shivam-Jha96 in #12
• Documentation Update - Usage Guides and Upgrade Commands by @Shivam-Jha96 in #13
• Fix Outdated Version Display & Dynamic README Badges by @Shivam-Jha96 in #14

Full Changelog: v1.0.3...v1.0.4