Skip to main content
Framed content
A release is a version of software and its compatible config schemas. Within a fleet of robots, multiple software versions may be deployed — each release defines which config schemas are valid for that version. For example, software release v1.7.0 might specify the following schemas:
Config TypeSchema Version
MobilitySCH-FmoDN
PerceptionSCH-3JcLq
ManipulationSCH-HHDRn
Before deploying config instances to a device, the deployment’s release (v1.7.0) is used to verify that all required config instances are present and that each instance complies with the release’s schemas.

​
Properties

​
version
string
A semantic version, unique for a given release.Versions must be dot-separated integers. You may optionally use a v prefix, a prerelease suffix (e.g. -alpha.X, -beta.X, -rc.X), or a build suffix (e.g. +build-metadata).Examples: v1, 1, v2.1, 2.1, v3.2.1, 3.2.1, v4.3.2-beta.1, 4.3.2-rc.1, v5.4.3+metadata, 6.5.4-beta.2+metadata
​
config schemas
[] Config Schema
The config schemas that define compatible config instances for the release.Examples: SCH-FmoDN, SCH-3JcLq, SCH-HHDRn