Skip to content
ABRQ DATADocs Abrq DIP · latest
Product page Request a trial
On this page

Release notes

About this page#

This repository keeps no CHANGELOG.md. The entries below are summarized from the release tags in the product repository and from the internal status log, so they describe what a release was about rather than enumerating every commit in it.

Read the entry for every version between the one you run and the one you are moving to — not only the target. Then follow Upgrade and rollback for the mechanics.

Note. Version numbers are the release tags (v1.4.1 and so on). The running build reports its own version and commit at GET /health.

1.4 line#

1.4.1 — 2026-07-10#

Maintenance release on the 1.4 line. No breaking changes; no operator action beyond the normal upgrade.

1.4.0 — 2026-06-29#

Feature release opening the 1.4 line. No breaking changes recorded at the tag. Upgrade in place from any 1.3.x, then confirm GET /health reports the new version before removing the previous image.

1.3 line#

1.3.3 — 2026-06-05#

Breaking — new signing keys. Licenses must be re-issued.

This release embeds a new pair of vendor public keys: one for license signatures and one for the release integrity manifest.

The consequences:

  • Licenses must be signed with the new vendor key. A license issued for 1.3.1 or earlier will not validate on 1.3.3 or later — the instance fails its startup license check.
  • The release manifest must be signed with the new manifest key, so an image built before the rotation will not satisfy the integrity check.

Upgrade action:

  1. Request a re-issued license before upgrading.
  2. Upgrade to 1.3.3 or later.
  3. Install the re-issued license, then start.

Skipping step 1 leaves the instance unable to start. See the license signature invalid and license not found rows in Troubleshooting for what that looks like.

1.3.1 — 2026-06-05#

Patch release on the 1.3 line. No breaking changes.

1.3.0 — 2026-06-04#

Two themes:

  • Configurable dashboard. The overview dashboard became operator-arrangeable rather than fixed.
  • Scheduler fix. A queue and event-loop defect in the scheduler was corrected. If you were seeing due work sit unclaimed, this is the release that addresses it.

No breaking changes. Note that 1.3.3 further down the same line is breaking — do not stop at 1.3.0 and assume the line is safe to roll forward without re-issuing licenses.

1.2 line#

1.2.1 — 2026-05-18#

Patch release. No breaking changes.

1.2.0 — 2026-05-17#

Feature release on the 1.2 line, tagged alongside end-to-end test corrections. No breaking changes.

1.1 line#

1.1.2 — 2026-05-14#

Compose template fix: the ABRQ_ALLOW_INSECURE and ABRQ_ENABLE_HSTS variables are now passed through to the container. Before this release, setting either one in the environment file had no effect on the running instance.

Upgrade action: if you had worked around this by editing the Compose file directly, re-check your file against the shipped template after upgrading.

1.1.0 — 2026-05-14#

First customer release. Fixed the application-server factory wiring and the license-file mount. This is the earliest version intended for production use; anything earlier is pre-release.

Upgrading#

  • Upgrades are forward-only through the release sequence. Do not skip a line without reading the entries in between — 1.3.3 in particular changes a cryptographic requirement that no later release relaxes.
  • Pin ABRQ_VERSION explicitly. An unset version is the usual cause of pull access denied during an upgrade.
  • The full procedure, including how to roll back and what a rollback does to migrated data, is in Upgrade and rollback.