> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/on-premise/es/versions.md).

# Registro de cambios

Dé seguimiento al historial de versiones de Navixy On-Premise por año. Cada compilación cubre nuevas integraciones de dispositivos, mejoras de la plataforma, correcciones de errores y scripts de actualización.

Siga el historial de versiones y las actualizaciones de los despliegues On-Premise de Navixy. El registro de cambios documenta integraciones, mejoras y problemas resueltos para compilaciones independientes.

**¿Qué incluye:**

* Nuevas integraciones de dispositivos y compatibilidad con soluciones de terceros
* Mejoras de la plataforma y mejoras de funcionalidades
* Correcciones de errores y actualizaciones de estabilidad
* Scripts para facilitar la instalación y la actualización

Explorar por año: <a href="/docs/on-premise/es/versions/2026.md" class="button primary">2026</a> <a href="/docs/on-premise/es/versions/2025.md" class="button primary">2025</a>

Si tiene preguntas sobre actualizaciones específicas o necesita asistencia con el despliegue, contacte al equipo de soporte de Navixy - <support@navixy.com>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/on-premise/es/versions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
