Skip to content

add GH releases to publishing docs #105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 5, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions resources/views/docs/desktop/1/publishing/publishing.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
title: Publishing
order: 200
---

## Publishing Your App

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

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

**Make sure you've bumped your app version in your .env file before building**

### Cross-compilation

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

**Cross-compilation is not supported on all platforms.**

### GitHub Releases

If you use the GitHub [updater provider](/docs/publishing/updating), you'll need to create a draft release first.

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.

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.