Checking application updates
Read the latest version and changelog as JSON, then download and verify the application ZIP.
Latest version and changes
Request the latest NQ2 Local version:
GET /api/apps/nq2-local/latest-version
The response is JSON with HTTP 200 and Content-Type: application/json.
| Field | Meaning |
|---|---|
application | Application identifier, currently nq2-local |
version | Highest published stable numeric version, such as 1.0.1 |
released_at | Release date in YYYY-MM-DD format |
changelog.en, changelog.pl | Lists of changes in English and Polish |
download_url | Address that always downloads the latest package |
archive_url | Address of this particular version’s archive |
release_notes_url | Human-readable release page |
size | Archive size in bytes |
sha256 | Archive SHA-256 checksum |
The response describes the latest available version. It does not know your
installed version: the client compares the three numeric version components.
For example, 1.10.0 is newer than 1.9.0. Use changelog.pl for Polish UI.
Download
Download the latest application ZIP:
GET /api/apps/nq2-local/download.zip
The checksum file is at /api/apps/nq2-local/download.zip.sha256.
Each application stores its versioned packages in its own directory, for example
/api/apps/nq2-local/downloads/1.0.1.zip. The matching checksum file adds
.sha256. The application page lists its releases and links to these packages.
After checking the version, an updater can use archive_url to fetch exactly
the version described in that response. Verify its size and SHA-256 before
installing. The latest-package address can change if another release is
published between checking and downloading.
Local development
Run hugo server and use the same paths on your local server:
curl --fail http://localhost:1313/api/apps/nq2-local/latest-version
curl --fail http://localhost:1313/api/apps/nq2-local/download.zip --output nq2.zip
Hugo generates these per-application endpoints directly, including during local development. Cloudflare Pages uses matching routing rules after deployment.
Hugo generates the API files as part of the build. No additional generator or backend is required.