# Release notes

URL: /release-notes

What changed in each Foxborne release, newest first, with the signing key and bill of materials the product states for it. Install a release as a signed bundle, and check its signature before it installs.



Foxborne ships as signed bundles, each with a software bill of materials. Each release below gives its change as the product records it, newest first. The same notes are published as an RSS feed at `/release-notes/rss.xml`.

## Foxborne 1.4.2 [#v1-4-2]

<Fields>
  <Field name="Published">
    10 September 2026
  </Field>

  <Field name="Signed by">
    Foxborne release key 

    `7C1E 4B90 3A2F 9A42`
  </Field>

  <Field name="Bill of materials">
    SPDX 2.3, 412 components, stored with the release
  </Field>

  <Field name="Example deployment">
    Installed on 12 Sep 2026
  </Field>
</Fields>

<Badge tone="mono">
  Fixed
</Badge>

* Parser fixes for PX4 v1.16 rover topics.

## Foxborne 1.4.1 [#v1-4-1]

<Fields>
  <Field name="Example deployment">
    Installed on 1 Sep 2026
  </Field>
</Fields>

<Badge tone="mono">
  New
</Badge>

* Receive log latency estimates from `SYSTEM_TIME`. See [Receiver JSONL records](/reference/receiver-jsonl#link-latency) for how latency enters a receipt's bound.

## Foxborne 1.4.0 [#v1-4-0]

<Fields>
  <Field name="Example deployment">
    Installed on 15 Aug 2026
  </Field>
</Fields>

<Badge tone="mono">
  New
</Badge>

* Manual clock alignment from matching events. See [Align a clock by hand](/investigate/align-a-clock).

## Install a release [#install-a-release]

An admin brings the release's `.fxb` bundle into your network and opens **Hosting**, **Install an update**; nothing is downloaded. Foxborne then reads the bundle and checks its signature against the Foxborne release key. It also checks the bill of materials and the database migration, and the install button stays disabled until every check is done.

The dialog notes &#x2A;*Downtime: none. Workers restart one at a time.** In the example dataset, the audit log records the 1.4.2 install as **Installed update**, with the detail **Signature verified, SBOM stored**.

[Install an update](/deploy/upgrades) walks through the whole procedure.

## Verify a release [#verify-a-release]

The **Updates** panel on **Hosting** shows the installed version, the key that signed it and its bill of materials. The version in the summary strip carries **Signature verified**. [Release signing and SBOM](/security/release-signing) covers the release key and the bill of materials in full.

## Follow new releases [#follow-new-releases]

Subscribe to the RSS feed at `/release-notes/rss.xml`. It carries one item per release, with its version and note, and the publication date where the release states one.

## Rule changes [#rule-changes]

Detection rules carry their own versions, which change when an admin saves a rule in your deployment. [Rule versions](/release-notes/rules) explains how, and how to trace every change in your audit log.