Skip to content

v2.1.13

Choose a tag to compare

@github-actions github-actions released this 27 Jun 06:55
d308ec3

Release Summary

sima-cli v2.1.13 focuses on making the Neat SDK setup and recovery experience smoother, especially after host restarts, Docker restarts, DevKit re-pairing, and Model Compiler extension installation.

This release also adds support for installing structured package artifacts from repository subfolders, which enables simpler install commands for packages such as Model Compiler examples.

Highlights

Easier Neat SDK Recovery

sima-cli sdk neat can now recover when the Neat SDK container already exists but is stopped. Instead of asking you to rerun SDK setup or recreate the container, sima-cli starts matching stopped Neat SDK container(s) and then continues with the original SDK shell or command flow.

This is most useful after restarting Docker, Colima, or the host machine.

Better DevKit Re-Pairing Behavior

When you re-run SDK setup against a DevKit, sima-cli now reissues the Neat SDK HTTPS certificate for the current host IP. This helps avoid stale certificate errors when the DevKit pairing changes, or when the host network path changes after VPN or network changes.

Cleaner Model Compiler Extension Setup

During Neat SDK setup, if you choose to install the Model Compiler extension, sima-cli now avoids an extra nested update confirmation prompt inside the container. The setup flow remains interactive where it should be, but the internal install step no longer interrupts you with a second sima-cli update question.

Package Install Paths Can Target Subfolders

sima-cli neat install now supports package metadata published under repository subfolders. This allows commands such as:

sima-cli neat install model-compiler/examples

This keeps install commands simple while allowing repositories to publish multiple artifact groups, such as SDK packages, examples, tools, or documentation bundles.

Clearer Docker Permission Guidance on Linux

For Linux users, sima-cli now gives clearer guidance when Docker is running but the current shell cannot access /var/run/docker.sock. If the user has been added to the docker group but the current shell has not picked up that group membership yet, sima-cli now provides deterministic next steps such as using newgrp docker or opening a new shell.

Maintainer and Release Workflow Updates

This release also includes repository workflow improvements that do not change normal CLI behavior:

  • PR metadata sanitization workflow support.
  • Release issue validation wiring.
  • Maintainer authorization before release-readiness validation can access release app credentials.
  • Initial sima-cli issue triage workflow support.

Upgrade Notes

Upgrade with your existing sima-cli update flow. No application code or SDK workspace migration is required for this release.

Full Changelog

v2.1.12...v2.1.13