This version was released on February 5, 2026.
We’re introducing Container Versioning, a new system that makes managing custom code containers simpler, safer, and more scalable for Design System teams.
Semantic versioning for containers
Containers now support multiple semantic versions (for example 1.0.0, 1.1.0, 2.0.0), grouped automatically by the container name from your package.json. You can manage all versions of the same container in one place instead of creating new contexts each time.
Update versions without recreating contexts
No more duplicating contexts just to ship an update. Design System teams can now:
- Upload new container versions
- Switch which version a context uses
- Create a new prototype to use the new container version
New work uses the latest version
The new container version is available only for new prototypes. To use it, create a new prototype in your project — not a new iteration of an existing one. Any new iterations within an existing prototype will stay on the same container version that prototype was started with — they do not regenerate with the new container.
When creating new prototypes in the project, the system automatically uses the most up-to-date container version selected in the shared context at that time. This helps teams stay current without extra steps.
Project contexts are now Shared contexts
To better reflect their purpose, Project contexts have been renamed to Shared contexts.
Functionality remains the
same, only the name has changed.
Notifications accessible in Portal projects
Based on customer feedback, we’ve added a notifications icon directly in the Project section, where you spend most of your time prototyping and writing docs. Now you can check updates without having to jump back to Home.
For a list of smaller improvements and bug fixes, visit our Bug fixes page here: