Skip to content

Commit 0def33f

Browse files
authored
Merge pull request #105 from NativePHP/prep/v1-publishing
2 parents 939bcef + d0bb23b commit 0def33f

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

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

+11
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
title: Publishing
33
order: 200
44
---
5+
56
## Publishing Your App
67

78
Publishing your app is similar to building, but in addition NativePHP will upload the build artifacts to your chosen
@@ -15,6 +16,8 @@ php artisan native:publish
1516

1617
This will build for the platform and architecture where you are running the build.
1718

19+
**Make sure you've bumped your app version in your .env file before building**
20+
1821
### Cross-compilation
1922

2023
You can also specify a platform to build for by passing the `os` argument, so for example you could build for Windows
@@ -27,3 +30,11 @@ php artisan native:publish win
2730
Possible options are: `mac`, `win`, `linux`.
2831

2932
**Cross-compilation is not supported on all platforms.**
33+
34+
### GitHub Releases
35+
36+
If you use the GitHub [updater provider](/docs/publishing/updating), you'll need to create a draft release first.
37+
38+
Set the "Tag version" to the value of `version` in your application `.env` file, and prefix it with v. "Release title" can be anything you want.
39+
40+
Whenever you run `native:publish`, your build artifacts will be attached to your draft release. If you decide to rebuild before tagging the release, it will update the artifacts attached to your draft.

0 commit comments

Comments
 (0)