Versioning
Last updated
Was this helpful?
Last updated
Was this helpful?
The bigger your system grows and the more libs or packages you integrate into your project, the more likely you are to face such a problem as dependency hell.
As a solution, code.store platform suggests relying on a simple set of rules and requirements that govern how version numbers are assigned and incremented. There are many approaches to software versioning and their interfaces, the choice is always up to the developer.
When you create a new service, by default, it deployed into private and demo and it's version is 0.0.1
To find out which version is in use execute cs service:info CLI command and select the service. You will find which versions deployed on private and demo environments.
On example above on the private environment deployed service with 0.0.2 version and 0.0.1 on the demo.
If you already include service to project, you can execute cs project:service:info CLI command, select project and service to display.
On example above deployed on three environments deployed next versions:
environment
version
development
0.0.3
staging
0.0.2
production
0.0.2
It's very important to increment service version after making changes to service. Actual service version is always available at package.json file.
To make a new version available - execute cs promote CLI command. This command will deploy changes from private to demo environment and makes a new version available for update/include into projects. Promoted version to demo environment is marks as LATEST
For example, if your project includes some service - you can promote only already deployed service version to another environments.
To update project service to latest version execute cs project:service:roll CLI command, where you can select project, environment where will be applied changes, service and version.
Select latest version if you need a latest available service version.
To rollback service version use the same command cs project:service:roll and just select needed version and environment where to deploy needed version.
To create a new version just push your changes using cs push CLI command. More information about pushing changes can be found in section. After pushing changes - a new version will be available on the private .
By default, code.store platform will automatically increment path (x.y.Z) version of your code after each push, if you follow specification.
After creating a new service version using cs push command - changes will be available only on the private .
demo - is the only place, where developed changes can be published. Changes from demo environment is available for including to the project or public .
When you include a new service to the - version from demo will be deployed. This allows adhering to the concept of public release of new versions to avoid unexpected system behavior. More information about including services to projects can be found in section.
After including service to the project - it's deployed only to development . To move service version to another environment use cs project:service:promote CLI command. It allows you to move already deployed version to another environment.