> 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/id/qa/software-updates/current-version.md).

# Versi saat ini

Temukan nomor versi platform Navixy On-Premise di file VERSION pada server Anda. Pahami skema penomoran build utama dan minor.

Informasi tentang versi platform Navixy yang diterapkan pada instance On-Premise Anda dapat ditemukan di file sistem layanan backend.

Untuk menemukan versinya, buka direktori layanan Java mana pun dan cari file bernama **VERSION**. Biasanya folder-folder ini adalah:

* Linux: `/home/java/api-server/VERSION`
* Windows: `C:\java\api-server\VERSION`

File VERSION adalah file teks biasa yang dapat dibuka dan dibaca dengan editor teks apa pun. Di dalam file, Anda akan menemukan informasi teknis, dan di bagian akhir akan ada baris yang menunjukkan versi platform. Baris tersebut memuat rincian berikut:

**navixy-standalone-provider.2023.02.166**

* navixy-standalone – menunjukkan bahwa ini adalah instance On-Premise;
* provider atau enterprise – jenis paket;
* 2023 – tahun rilis;
* 02 – versi build mayor, yang biasanya sesuai dengan bulan rilis
* 166 - versi build minor, diberi nomor berurutan

Versi mayor platform dirilis setiap 2-3 bulan dan memuat inovasi signifikan serta fitur baru.

Versi minor dapat dirilis beberapa kali per bulan, dan mencakup peningkatan kecil serta perbaikan bug yang tidak memerlukan perubahan signifikan pada kode platform.


---

# 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/id/qa/software-updates/current-version.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.
