Overview
Every Codenull application runs on a specific version of the platform (the backend and the user interface always come from the same version, so they are always compatible with each other). The platform interface is built once per release and reused by all applications. When your application is generated or redeployed, it picks up the prebuilt interface that matches its version — this keeps deployments fast (a couple of minutes) and guarantees that every application on the same version behaves exactly the same.Choosing a version
Each application has a platform version setting that controls which version it runs on:| Setting | What your application gets |
|---|---|
(empty) or main | The latest platform updates, as soon as they are available. Recommended for development and test applications. |
A release number, e.g. 3.10.0 | That exact platform release. The application stays on it until you change the setting. Recommended for production applications that need predictable behavior. |
| A preview name provided by the Codenull team | A pre-release version, used to validate an upcoming fix or feature before it is officially released. |
Staying on the latest version
Applications without a pinned version always follow the most recent platform updates. Each time the application is redeployed it picks up whatever is current at that moment.Pinning a release
Pinning to a release number (for example3.10.0) freezes the platform for that application. Redeploying does not change its behavior — you decide when to move to a newer release by updating the setting. Published releases are never modified, so a pinned application is fully reproducible.
You can check the platform release history in the changelog.
Trying a preview version
Sometimes the Codenull team will ask you to validate a fix or a new capability before it is released. In that case they will give you a preview name to put in the version setting. Preview versions:- Are updated continuously while the fix or feature is being worked on (redeploy to get the newest state).
- Are temporary — once the change is released, switch the application back to the latest version or pin the new release number.
- Never affect other applications or published releases.
What this means for you
- Fast deployments: creating or updating an application takes a couple of minutes.
- Consistency: two applications on the same version always have an identical interface and behavior.
- Safe releases: production applications pinned to a release are not affected by ongoing platform development.
- Easy validation: previews let you confirm a fix in your own application before it ships.