I have a Docker-based build pipeline that:

• Inside the voxl-cross:2.7 container, installs ModalAI packages

DEPS="
libmodal-pipe
"
PLATFORM=qrb5165
SECTION=sdk-1.4

# Add to /etc/apt/sources.list.d
DPKG_FILE="/etc/apt/sources.list.d/modalai.list"
LINE="deb [trusted=yes] http://voxl-packages.modalai.com/ ./dists/$PLATFORM/$SECTION/binary-arm64/"
sudo echo "${LINE}" > ${DPKG_FILE}

## Update package index
sudo apt-get update -o Dir::Etc::sourcelist="sources.list.d/modalai.list" -o Dir::Etc::sourceparts="-" -o APT::Get::List-Cleanup="0"

## Install dependencies
sudo apt install -y $DEPS

• Inside the same container, builds my application

Over the weekend my build broke due to an incompatibility between the newly released libmodal-pipe_2.13.1_arm64.deb (released to the sdk-1.4 apt repository) and the voxl-cross:2.7 build container.

My workaround has been to pin the version of the libmodalpipe apt package I install: libmodal-pipe=2.10.6.

How should I think about versioning guarantees between the SDK version and the voxl-cross container version? Should I expect packages in a given SDK version to continue to build in a given voxl-cross container version? Or is your recommendation to live at the bleeding edge of the voxl-cross container version?