> For the complete documentation index, see [llms.txt](https://chrondb.avelino.run/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chrondb.avelino.run/releases/next.md).

# Release Notes

This is the first official release of ChronDB, a chronological key/value database based on a Git architecture.

## Main Features

### Schema Validation

* **Optional JSON Schema Validation** - Per-namespace validation with configurable modes (strict/warning/disabled) ([#55](https://github.com/avelino/chrondb/issues/55))
  * REST API endpoints for schema management (`/api/v1/schemas/validation`)
  * Redis commands (`SCHEMA.SET`, `SCHEMA.GET`, `SCHEMA.DEL`, `SCHEMA.LIST`, `SCHEMA.VALIDATE`)
  * SQL DDL statements (`CREATE/DROP/SHOW VALIDATION SCHEMA`)
  * Supports JSON Schema Draft-07, 2019-09, and 2020-12
  * Version-controlled schema history

### Communication Protocols

* **PostgreSQL Protocol Support** - Implementation of the PostgreSQL protocol for communication with ChronDB, allowing compatibility with existing PostgreSQL tools and clients ([#16](https://github.com/avelino/chrondb/pull/16))
* **Redis Protocol Server Implementation** - Support for the Redis protocol, expanding database communication options ([#11](https://github.com/avelino/chrondb/pull/11))

### Storage

* **Virtual Git Storage Implementation** - Rewrite of the Git storage implementation to use virtual commits, improving performance and scalability ([#9](https://github.com/avelino/chrondb/pull/9))
* **File Repository Support** - Added support for file-based storage ([#6](https://github.com/avelino/chrondb/pull/6))
* **Initial JSON Compression** - Implementation of JSON compression to optimize data storage ([#1](https://github.com/avelino/chrondb/pull/1))

## Performance Improvements

### SQL Driver

* **Removal of Unnecessary GROUP BY Operations** - Fixed an issue where the GROUP BY clause was being unnecessarily applied in SQL queries, significantly improving performance ([#17](https://github.com/avelino/chrondb/pull/17))
* **Client Connection Handling Improvements** - Optimization of connection handling for greater stability and performance ([#17](https://github.com/avelino/chrondb/pull/17))

## Tools and Utilities

* **Diagnostic and Dump Tools** - Added new tools for diagnostics and data dumping, facilitating debugging and analysis ([#17](https://github.com/avelino/chrondb/pull/17))

## Refactoring and Internal Improvements

* **New Package Architecture** - Restructuring of the package architecture for better code organization and maintainability ([#7](https://github.com/avelino/chrondb/pull/7))
* **GitHub Actions and Binding Renaming** - Implementation of GitHub Actions for continuous integration and adjustments to binding names ([#2](https://github.com/avelino/chrondb/pull/2))

## Note

This release represents the collaborative effort of the community to create a robust and efficient chronological key/value database. We thank all contributors who made this version possible.

### Licensing Update

* ChronDB is now distributed under the GNU Affero General Public License v3.0 (AGPLv3) to ensure modifications deployed as network services remain available to the community.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://chrondb.avelino.run/releases/next.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.