Releases and Versions
Releases package the deployable artefacts for a marketplace product.
Create releases from the product page in the Infuse Cloud dashboard. Each release needs a binary and a manifest.
Before You Start
Prepare:
- the deployable binary,
- a JSON or YAML manifest,
- release notes or a change log,
- an optional availability date.
Manifest Format
Manifests can be JSON or YAML. They must contain an application object.
application:
version: 1.2.0
id: 10042
primary: pump-monitor
board: infuse/boards/pump-controller
soc: nrf5340
network_id: 7
TF-M: true
sysbuild: true
Required fields:
| Field | Required for | Notes |
|---|---|---|
application.version | Apps and algorithms | Must be semantic versioning, such as 1.2.0. |
application.id | Apps and algorithms | Must be a positive integer. |
application.board | Apps | Used to resolve the target board. |
Optional fields include primary, soc, network_id, TF-M, and sysbuild. Extra manifest fields are preserved as extension metadata.
Algorithms do not require application.board; apps do.
In the Dashboard
- Open Marketplace.
- Select the marketplace instance.
- Open Developer.
- Open Manage.
- Open the product.
- Open Releases.
- Click Create Release.
- Upload the binary.
- Upload the manifest.
- Confirm the detected manifest version.
- Add release notes.
- Set Available from if the release should become active later.
- Create the release.
After creation, the release appears in the release history. Review the version, availability, release notes, and binary metadata before publishing.
What Happens Behind the Scenes
The dashboard uploads the binary and manifest as completed assets, then creates a marketplace item release. The manifest is parsed during release creation. Its application.version becomes the marketplace release version, so versions must be unique per product and must follow semantic versioning.
Release creation fails when:
- the product does not belong to the developer organisation,
- either asset is missing, incomplete, or the wrong type,
- the binary already has marketplace binary metadata assigned,
- the manifest is invalid,
- the manifest version is not semantic,
- the version already exists for the product.
API Equivalent
POST /marketplace/developers/marketplace-items/{id}/releases
Authorization: Bearer {developer_access_token}
Content-Type: application/json
{
"binaryAssetId": "44444444-4444-4444-4444-444444444444",
"manifestAssetId": "55555555-5555-5555-5555-555555555555",
"availableFrom": "2026-06-01T00:00:00Z",
"changeLog": "Adds board compatibility metadata and improves startup diagnostics."
}
If availableFrom is omitted, the release is available immediately. If provided, it must be in the future.
GET /marketplace/developers/marketplace-items/{id}/releases?page=1&pageSize=20
Authorization: Bearer {developer_access_token}