Upgrading to a New Release
Each platform is its own GitHub repository, with the Arino One template as upstream.
Merge the Release
Merge the new release by pull request, so you can review every change.
Migrations
The release's database migrations bring your schema up to date. Until then a schema-behind banner shows.
Checks and Test Messaging
Run the checks, then Test Messaging to confirm messages still send.
Customise Only in the src/custom Folder
Keep your own changes in src/custom and upgrades stay clean.
Steps at a glance
- Check Your VersionOpen /settings/about to see your current release.
- Open a Pull RequestIn your own GitHub repository, merge the new release from the template upstream by pull request.
- Apply MigrationsLet the release's database migrations run.
- Run the ChecksRun the checks and use Test Messaging to confirm messages still send.
- Confirm the Banner Is GoneThe schema-behind banner disappears once the schema matches the release.
Frequently asked
Where Does My Code Live?
In your own GitHub repository. The Arino One template is set as upstream.
Will My Changes Be Overwritten?
Not if you customise only in src/custom, which releases never touch.
What Does the Schema-Behind Banner Mean?
Your database is behind your release; apply the migrations.
How Do I Know Messaging Still Works?
Run Test Messaging after the merge.
Apply this to your own deployment
This guide describes decisions we make on live platforms. Tell us your channels, systems and region and we will map it to an architecture outline, a provisioning plan and an indicative commercial model — usually within one business day.