Show and tell: mise plugin for reproducible Zephyr SDK installs

[BuriKizilkaya]

Hi everyone,

I built mise-zephyr-sdk, a mise plugin for installing the Zephyr RTOS SDK from mise.toml.

Repository: https://github.com/klab365/mise-zephyr-sdk

The goal is to make Zephyr SDK setup reproducible across developer machines and CI. Instead of keeping SDK installation as a separate manual checklist, a project can declare the SDK version and required SDK toolchains in its mise.toml.

Example:

[plugins]
zephyr-sdk = "https://github.com/klab365/mise-zephyr-sdk.git"

[env]
ZEPHYR_SDK_TOOLCHAINS = "x86_64-zephyr-elf arm-zephyr-eabi"

[tools]
zephyr-sdk = "0.17.4"
cmake = "3"
ninja = "latest"
uv = "0.11.6"

Then:

mise trust
mise install

The plugin handles the Zephyr-specific parts of SDK installation:

• downloads the matching Zephyr SDK minimal tarball for Linux/macOS and host architecture
• runs the Zephyr SDK setup.sh after extraction
• installs only the SDK toolchains configured by the project
• exports ZEPHYR_TOOLCHAIN_VARIANT=zephyr
• exports ZEPHYR_SDK_INSTALL_DIR so Zephyr/CMake can find the SDK
• rejects ZEPHYR_SDK_TOOLCHAINS=all to avoid unexpectedly large SDK installs

Current status:

• Linux and macOS are supported on x86_64/aarch64
• native Windows is not supported; WSL is the intended path
• release metadata comes from zephyrproject-rtos/sdk-ng
• release asset SHA256 digests are used when available
• the repository includes a minimal hello-world Zephyr example and GitHub Actions workflow
• license: Apache-2.0

I would appreciate feedback from Zephyr and mise users, especially on:

• whether ZEPHYR_SDK_TOOLCHAINS feels like the right project-level configuration point
• which example SDK toolchains would be most useful in documentation
• whether there are platform or CI cases I should cover
• whether the plugin behavior matches expectations for Zephyr SDK setup

Thanks, and feedback is very welcome.