Update docs to explain version update needed to trigger migrations in app update (#34)

* note that a version update is needed

* Versioning

---------

Co-authored-by: Simon Hamp <[email protected]>

Author: alnutile

resources/views/docs/1/publishing/building.md

@@ -17,6 +17,17 @@ your app to provide automatic updates.
 You should build your application for each platform you intend to support and test it on each platform _before_
 publishing to make sure that everything works as expected.
 
+## Versioning
+
+For every build you create, you should change the version of your application in your app's `config/nativephp.php` file.
+
+This can be any format you choose, but you may find that a simple incrementing build number is the easiest to manage.
+
+**Migrations will only run on the user's machine if the version reference is _different_ to the currently-installed version.**
+
+You may choose to have a different version number that uses a different scheme (e.g. SemVer) that you use for user-facing
+releases.
+
 ## Running a build
 
 ```shell

yarn.lock

@@ -7,10 +7,10 @@
   resolved "https://registry.npmjs.org/@alloc/quick-lru/-/quick-lru-5.2.0.tgz"
   integrity sha512-UrcABB+4bUrFABwbluTIBErXwvbsU/V7TZWfmbgJfbkwiBuziS9gxdODUyuiecfdGQ85jglMW6juS3+z5TsKLw==
 
-"@esbuild/win32[email protected]":
+"@esbuild/linux[email protected]":
   version "0.17.19"
-  resolved "https://registry.npmjs.org/@esbuild/win32-x64/-/win32-x64-0.17.19.tgz"
-  integrity sha512-lAhycmKnVOuRYNtRtatQR1LPQf2oYCkRGkSFnseDAKPl8lu5SOsK/e1sXe5a0Pc5kHIHe6P2I/ilntNv2xf3cA==
+  resolved "https://registry.npmjs.org/@esbuild/linux-x64/-/linux-x64-0.17.19.tgz"
+  integrity sha512-68ngA9lg2H6zkZcyp22tsVt38mlhWde8l3eJLWkyLrp4HwMUr3c1s/M2t7+kHIhvMjglIBrFpncX1SzMckomGw==
 
 "@jridgewell/gen-mapping@^0.3.2":
   version "0.3.3"