Is there a defined support lifecycle / EOL / LTS policy for Isaac Sim releases?

[prakash-aryan]

The 5.1.0 docs carry an “Isaac Sim 5.1.0 is no longer supported” banner, but I cannot find any stated support window, lifecycle, or EOL policy for Isaac Sim releases anywhere in the docs.

For context on the release cadence:

• Isaac Sim 5.1.0 was released on 2025-10-21
• It became unsupported when Isaac Sim 6.0.0 GA was released on 2026-06-04
• Isaac Sim 6.0.1 followed only 18 days later, from 2026-06-04 → 2026-06-22

Could you clarify the following?

1. Support window / LTS

   • Is there a defined support window per release?
   • Is there an LTS branch?
   • How long will the 6.0.x line receive bug and security fixes?

2. Patch support policy

   • When a patch release lands, for example 6.0.0 → 6.0.1, is the prior patch immediately considered unsupported?
   • Or is the whole 6.0.x minor line supported until the next minor or major release?

3. Recommended practice for stable pinned versions

   • What is the recommended practice for projects that need to pin a stable Isaac Sim version for several months, especially for sim-to-real experiments and reproducibility?
   • How can such projects avoid being on an “unsupported” build while maintaining reproducibility?

Thanks!

[vick-yu]

We are checking this with our team and will get back to you as soon as we have an update.

[vick-yu]

Isaac Sim release and support lifecycle

Isaac Sim follows a latest-release support model. We welcome issue reports from users of any version; however, an issue may already be resolved in the latest generally available (GA) release. Before reporting an issue, we encourage users to test with the latest GA release, when possible, and confirm whether the issue still occurs.
Bug fixes are generally delivered in the latest or a future release rather than backported to earlier versions. When reporting an issue, please include the Isaac Sim version used and the results of any testing performed with the latest GA release.

[d-kleine]

Is there any plan for a public roadmap? From a user's perspective, this would be helpful for having a rough timeline for upcoming releases, such as for when a fix for a reported issue can be expected.

[vick-yu]

Thanks for the feedback— I've shared your concern and suggestion with our team. At the moment, we don't intend to provide that kind of information, including for upcoming release. I'll update here if that changes.

[vick-yu]

BTW, the next release (6.1)  will most likely be end of August or early September. FYI.

[d-kleine]

Alright, thanks!

[vick-yu]

Our team has confirmed that the only information currently shareable throught community platforms is the upcoming release. If you run into further questions or need help with version pinning strategies in a future release, feel free to open a new discussion and reference this one for context. We appreciate the feedback on the roadmap request — we'll keep the community updated if that changes.