When you make changes to your components, markdown files, or styling, create a new version so teams can adopt updates without breaking existing work.
Version workflow
- Make your changes to components, AI markdown guides or other container files
- Update version in package.json: we recommend semantic versioning (e.g., 1.0.0 → 1.1.0)
- Upload via CLI – use the same CLI upload command you’ve used before to upload the container
supernova template-upload -w [WORKSPACE_ID] -d [DESIGN_SYSTEM_ID]
- New version appears in the code containers list in Design System Platform
- Workspace admins can then update which version is active in each shared context
Version behavior
Existing prototypes: Always use the container version they were created with. Uploading a new version never affects work in progress.
New prototypes: Use whatever version is currently set in their shared context. If a workspace admin updates the context to a newer version, all new prototypes created with that context will use the new version.
Uploading the same version twice
If you try to upload a container version that already exists, you'll get an error. For quick iterations during development, you can use the --force flag to override — but we don’t recommend using it for regular version updates.