Code version directories and the active code version
Key Takeaway
The storefront runs only the active code version. Code you upload to an inactive version has no effect on the storefront until you activate that version.
In B2C Commerce, your custom code lives in code versions. An instance can store several code versions at once, but it runs only one of them: the active code version. Because of this, you can build and test a new release while the storefront keeps running on a stable one. If the new release causes problems, you can roll back.
Code versions and the active code version
You can upload several code versions to an instance at the same time. You can name each one for its release, for example v12 or summer_release.
Each instance uses one active code version. All templates, pipelines, scripts, and images come from that version, so code in an inactive version has no effect on the storefront until you activate it.
Uploading cartridges into an inactive version is a normal step when you prepare a release, so the upload works on a sandbox. The storefront still keeps running the active version until you activate the version you uploaded to.
A team has v12 active on their instance. They create a new code version called summer_release and upload new templates and images into it over WebDAV. Shoppers still see the templates and images from v12, because summer_release isn't active yet. When the team is ready, they activate summer_release. From that moment, the server looks up resources in summer_release instead of v12, and the new templates appear on the storefront.