> 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/fr/versions.md).

# Journal des modifications

Suivez l’historique des versions Navixy On-Premise par année. Chaque build couvre les nouvelles intégrations d’appareils, les améliorations de la plateforme, les corrections de bugs et les scripts de mise à jour.

Suivez l'historique des versions et les mises à jour des déploiements On-Premise de Navixy. Le journal des modifications documente les intégrations, les améliorations et les problèmes résolus pour les versions autonomes.

**Ce qui est inclus :**

* Nouvelles intégrations d'appareils et prise en charge de solutions tierces
* Améliorations de la plateforme et des fonctionnalités
* Corrections de bogues et mises à jour de stabilité
* Scripts facilitant l'installation et la mise à jour

Parcourir par année : <a href="/docs/on-premise/fr/versions/2026.md" class="button primary">2026</a> <a href="/docs/on-premise/fr/versions/2025.md" class="button primary">2025</a>

Pour toute question concernant des mises à jour spécifiques ou une assistance au déploiement, contactez l'équipe d'assistance 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/fr/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.
