Release v2.1.2.2

This patch release improves SDK installation, DevKit recovery, and the SDK-to-DevKit workflow for SDK 2.1 users. It focuses on making the SDK easier to install, more resilient when host-to-DevKit file sharing cannot use NFS, and more reliable when reconnecting a paired DevKit.

If you use the SDK with a connected Modalix DevKit, this release is recommended.

What is new

One-command SDK installation through sima-cli

The SDK is now published with a sima-cli install package stub. This lets users install the SDK through the standard Neat package flow instead of manually pulling the container image first and then running SDK setup as a separate step.

To install and set up the latest SDK 2.1 release channel, run this command from the host:

sima-cli neat install sdk@release-2.1

To install the specific version:

sima-cli neat install sdk@v2.1.2.2

The command downloads the SDK image, starts the SDK setup flow, and prompts you to pair with a DevKit when available. Older SDK releases that predate this package continue to use the previous two-step image pull and setup process.

DevKit Sync fallback when NFS is unavailable

DevKit Sync can now fall back to rsync-over-SSH when NFS setup or mounting does not succeed. This helps users continue working in environments where SSH to the DevKit is available but NFS cannot be configured because of host networking, firewall, operating system, or policy constraints.

When rsync fallback is active, the SDK keeps the host and container workspace as the source of truth and synchronizes the relevant workspace scope to the DevKit before running commands with dk.

Neat Insight URL stays current after DevKit re-pairing

When the SDK is re-pointed to a different DevKit, Neat Insight now keeps its DevKit URL information updated through a supervised wrapper. This reduces stale URL behavior after changing the paired DevKit.

Updated Neat components

The SDK manifest now includes:

• Neat Library 0.2.2
• Neat Insight 0.0.4

These updates bring the latest SDK 2.1-compatible Neat runtime and Insight improvements into the default SDK environment.

Why this matters

The SDK is often used in environments where host networking, NFS permissions, corporate firewall rules, or DevKit storage layout can vary significantly. Previously, a failed NFS setup could block the expected shared-workspace workflow even when SSH access to the DevKit was working.

This release gives the SDK a more resilient fallback path. It also simplifies the first-time install path, improves behavior after changing the paired DevKit, and updates the default Neat and Insight components included with the SDK.

The result is a smoother setup experience and a more reliable edit-build-run loop across the host, SDK container, and Modalix DevKit.

User benefits

• Simpler SDK installation through the standard sima-cli package flow.
• Fewer setup failures when NFS is blocked or unavailable but SSH to the DevKit works.
• Better behavior when switching the SDK pairing from one DevKit to another.
• Updated Neat Library 0.2.2 and Neat Insight 0.0.4 selected by default from the SDK manifest.

Compatibility

This release remains on the SDK 2.1.2 platform baseline. The SDK release version is v2.1.2.2, while the platform compatibility version remains 2.1.2.

Users should continue using DevKit images that match platform version 2.1.2.

Included changes

• Add DevKit rsync fallback when NFS setup fails in #67
• Publish the SDK sima-cli install package stub in #82
• Keep the Neat Insight DevKit URL updated after DevKit re-pointing in #83
• Include Neat Library 0.2.2 and Neat Insight 0.0.4 in the SDK manifest
• Add release issue validation, PR sanitization, and issue triage automation in #75, #77, and #86
• Promote the patch contents through main and release-2.1 in #84 and #90

Full Changelog: v2.1.2.1...v2.1.2.2