Community registry: v0.2.2 release not indexed; extension id was renamed in this version

Omniverse Core Platform Extensions
1

Operating System:
Windows
Linux
Kit Version:
110 (Kit App Template)
109 (Kit App Template)
108 (Kit App Template)
107 (Kit App Template)
106 (Kit App Template)
105 (Launcher)
Kit Template:
USD Composer
USD Explorer
USD Viewer
Custom

Repository: GitHub - VicOne-OSS-TW/labr7-radeis-InSimPhysicalAI: In-Sim Physical AI Safety Validator — red-team your robot's VLM/VLA policy with adversarial scenarios in NVIDIA Isaac Sim. · GitHub
Public, tagged with the topic omniverse-kit-extension.

This repository is already present in the community registry under the
extension id labr7.radeis.redteam (versions 0.2.0 and 0.2.1).

NOTE ON THE FORM FIELDS
This is not a Kit App Template project. The extension targets NVIDIA Isaac Sim
(5.0.0-rc.45, which bundles Kit SDK 107.3), so I selected “107” / “Custom” as
the closest available options.

The extension declares no Kit version pin – extension.toml only sets
[package.writeTarget] kit = true. The +106.4.0 suffix on our existing index
entries (labr7.radeis.redteam-0.2.1+106.4.0) comes from the publishing
pipeline’s own Kit version (publish.kitVersion =
“106.4.0+release.156974.9321c814.gl”), not from anything we declare.

WHAT CHANGED IN 0.2.2
In v0.2.2 we renamed the extension id:
old: labr7.radeis.redteam
new: vicone.labr7.radeis
The Python package moved with it (labr7/radeis/redteam/ → vicone/labr7/radeis/).

RELEASE DETAILS (v0.2.2)
Released: 2026-08-31 09:01 UTC
Asset: VicOne-OSS-TW-labr7-radeis-InSimPhysicalAI-linux-x86_64-v0.2.2.zip
(15,097,021 bytes)
ZIP layout: exts/vicone.labr7.radeis/… (exts/ at archive root)
Manifest: exts/vicone.labr7.radeis/config/extension.toml
[package] name = “vicone.labr7.radeis”
[package] version = “0.2.2”

CURRENT STATE (checked 2026-09-03)
Reading the community registry index directly:

https://dw290v42wisod.cloudfront.net/exts/kit/community/3/index.zip

it contains only:
labr7.radeis.redteam-0.2.0+106.4.0
labr7.radeis.redteam-0.2.1+106.4.0

There is no vicone.labr7.radeis entry.

For reference, our previous release was indexed the next day:
v0.2.1 released 2026-08-07 14:36 UTC
indexed with publish.date = 2026-08-08 10:12 UTC

To be clear about what I am reporting: this is the contents of the registry
index file itself, not the community extensions report page on the docs site.
I am aware those are updated separately – see

REQUESTS

  1. Please index v0.2.2 under the new extension id vicone.labr7.radeis.

  2. How should an extension id rename be handled on the registry side? The old
    labr7.radeis.redteam entries will remain at 0.2.1 and will never receive
    an update, so existing users see no update is available. Can the old id be
    deprecated, removed, or pointed at the new one?

2

Ok, let me forward over to the correct person.

3

Hi, just following up—are there any updates on this? Thanks!

4

Let me ask you a clarifying question. Are you saying that your extension is successfully uploaded, but the kit registry is showing the older version of the extension?

5

Yes, with one important distinction: the extension ID was renamed in v0.2.2.

v0.2.1 is already available in the Isaac Sim Extension Manager under the old package name:

labr7.radeis.redteam — v0.2.1

For v0.2.2, we renamed the package/extension ID to:

vicone.labr7.radeis — v0.2.2

v0.2.2 has been successfully released on GitHub with the required Linux package:

However, vicone.labr7.radeis does not appear in the Community Registry or in the Isaac Sim Extension Manager at all. The registry still contains only v0.2.0 and v0.2.1 under the old labr7.radeis.redteam ID.

So this is slightly different from the registry simply showing an older version of the same extension ID. The GitHub repository is the same, but the extension ID changed in v0.2.2.

Could the ID change be why the publishing pipeline is not indexing v0.2.2? If an extension ID rename requires a specific migration step on the registry side, please let us know what we should do.

6

Maybe renaming it has caused an issue. Let me forward to the registry team.

7

Hi Richard,

Any updates from the registry team?

It appears the publishing pipeline does not support package ID changes. Could you please confirm whether this will be supported and provide an estimated timeline?

Thanks.

8

Hi and thanks for your patience. Ok, so we found out that actually the API token had expired for the push, and so we are fixing that as we speak. Hopefully that should solve a lot of the problems. I am not sure about changing the name or ID of an extension. I will have to ask about that.

9

Hi Richard,

vicone.labr7.radeis v0.2.2 has appeared in the Isaac Sim Extension Manager. Thanks a lot for your help!

However, the old extension, labr7.radeis.redteam v0.2.1, is still listed in the Extension Manager. Would it be possible to remove it?