> ## Documentation Index
> Fetch the complete documentation index at: https://docs.resurs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Stay informed about the latest updates, improvements, and changes to our platform

Welcome to our changelog. This section documents all updates, new features, improvements, and bug fixes across our platform. We're committed to transparency and keeping you informed about how our product evolves.

## What you'll find here

<CardGroup cols={2}>
  <Card title="New features" icon="sparkles">
    Discover the latest capabilities and functionalities added to the platform.
  </Card>

  <Card title="Improvements" icon="arrow-up">
    Learn about enhancements to existing features and performance optimizations.
  </Card>

  <Card title="Bug fixes" icon="wrench">
    Review resolved issues and stability improvements.
  </Card>

  <Card title="Breaking changes" icon="triangle-alert">
    Stay aware of important changes that may require action on your part.
  </Card>
</CardGroup>

## Stay updated

We release updates regularly to improve your experience and add value to our platform. Each changelog entry includes:

* **Version number** and release date for reference
* **Detailed descriptions** of what changed and why
* **Code examples** when relevant to demonstrate new features
* **Migration guides** for breaking changes

## How to read changelog entries

Each update is organized chronologically, with the most recent changes appearing first. Updates are categorized to help you quickly find relevant information:

* **New Features**: Brand new functionality added to the platform
* **Improvements**: Enhancements to existing features, performance, or user experience
* **Bug Fixes**: Resolved issues and stability improvements
* **Deprecations**: Features or APIs being phased out with migration guidance
* **Security**: Security-related updates and patches

<Info>
  If you have questions about any update or need help implementing changes, refer to our main documentation or contact our support team.
</Info>