Stride cli/1.0.1 Released
Stride cli/1.0.1 is a patch release for the engine’s command-line tooling, and it keeps the scope tight: one targeted fix for cross-platform use. The headline change is that the asset compiler can now be launched via dotnet outside Windows, which directly addresses issue #3256.
In practice, that matters for studios and solo developers who rely on automated builds, CI jobs, or Linux/macOS development environments. Before this fix, the CLI’s asset pipeline had a Windows-only limitation that could get in the way of consistent content processing across machines.
This release doesn’t introduce a broad feature set or API shake-up, but it does remove a real workflow snag for teams using Stride in mixed-platform setups. If your build scripts or tooling previously depended on a Windows host for asset compilation, cli/1.0.1 should make that path cleaner and easier to standardize.
Because this is a 1.0.1 patch, the expectation is stability rather than new surface area. The practical takeaway is simple: if you use Stride’s CLI for asset compilation, this update is worth pulling in to reduce platform friction.
- what
- Stride cli/1.0.1 patch release fixes the CLI asset compiler so it can run via dotnet off Windows.
- who
- Stride engine maintainers.
- when
- Released as cli/1.0.1; changelog compares cli/1.0.0 to cli/1.0.1.
- impact
- Improves cross-platform build and asset-processing workflows for developers using Stride CLI.
Small but useful cross-platform fix for build workflows
Follow stride updates
See relevant stories in your personalized news feed.
Discussion