Stride cli/1.0.0 Released

Stride CLI 1.0.0 is out, and this release focuses on making project maintenance and upgrades less painful for developers working in the Stride ecosystem. The biggest addition is generate-legacy-shader-code support for 4.0–4.3 projects, which should help teams keep older content pipelines moving without having to hand-roll compatibility fixes.

Upgrade flows also get smarter. The CLI now includes an 'sdk available' check and an auto-install target in upgrade, which should reduce the friction of moving projects forward when the required SDK isn’t already present. In practice, that means fewer manual setup steps and less time spent chasing environment issues before you can actually build or migrate.

There’s also a resolution change for --version: Stride now prefers template packages explicitly marked as compatible over newer packages that aren’t marked. That’s a subtle fix, but it matters for reproducibility, since it helps the CLI choose the version that is most likely to work with your project instead of simply grabbing the latest one.

This looks like a focused CLI release rather than a major engine milestone, but it’s the kind of update that can save time for tools programmers and technical teams managing multiple Stride versions. The release is tagged 1.0.0, and the full changelog compares cli/1.0.0-beta1 to cli/1.0.0.