Skip to content

Commit

Permalink
Updated readme and updated more actions pacakges.
Browse files Browse the repository at this point in the history
  • Loading branch information
jigar-f committed Jun 14, 2024
1 parent 7edd9a8 commit 6c1eb44
Show file tree
Hide file tree
Showing 9 changed files with 35 additions and 14 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/browerstack.yml
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ jobs:
- run: flutter --version

- name: Setup Go
uses: actions/setup-go@v4
uses: actions/setup-go@v5
with:
go-version-file: "go.mod"

Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/build-android.yml
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ jobs:
flutter-version-file: pubspec.yaml

- name: Setup Go
uses: actions/setup-go@v4
uses: actions/setup-go@v5
with:
go-version-file: "go.mod"

Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/build-darwin.yml
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ jobs:
run: git lfs pull

- name: Setup Go
uses: actions/setup-go@v4
uses: actions/setup-go@v5
with:
go-version-file: "go.mod"

Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/build-ios.yml
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ jobs:
run: git lfs pull

- name: Setup Go
uses: actions/setup-go@v4
uses: actions/setup-go@v5
with:
go-version-file: "go.mod"

Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/build-linux.yml
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ jobs:
sudo apt-get install -y libgtk-3-0 libblkid1 liblzma5
sudo apt-get install -y libpcap-dev libgtk-3-dev libayatana-appindicator3-dev ruby ruby-dev && sudo gem install bundler -v 2.2.26
- uses: actions/setup-go@v4
- uses: actions/setup-go@v5
with:
go-version-file: "go.mod"

Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/build-windows.yml
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ jobs:
run: git lfs pull

- name: Setup Go
uses: actions/setup-go@v4
uses: actions/setup-go@v5
with:
go-version-file: "go.mod"

Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/go.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ jobs:
- name: Install libpcap
run: sudo apt-get install libpcap-dev
- name: Set up Go
uses: actions/setup-go@v4
uses: actions/setup-go@v5
with:
go-version-file: "go.mod"
- name: Granting private modules access
Expand Down
6 changes: 3 additions & 3 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -172,17 +172,17 @@ jobs:
name: windows64-installer-signed

- name: Download the apk build output
uses: actions/download-artifact@v3
uses: actions/download-artifact@v4
with:
name: android-apk-build

- name: Download the aab build output
uses: actions/download-artifact@v3
uses: actions/download-artifact@v4
with:
name: android-aab-build

- name: Download the IPA
uses: actions/download-artifact@v3
uses: actions/download-artifact@v4
with:
name: Lantern.ipa

Expand Down
29 changes: 25 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -227,9 +227,13 @@ Do this to make a release build:
- Run `VERSION=<version here> make android-release ANDROID_ARCH=all`
- Or, `DEVELOPMENT_MODE=true make android-release ANDROID_ARCH=all` to enable "Development Mode" which has extra dev features like taking screenshots and dev settings.

### Building release packages
### 📦 Building Release Packages and Distributing the App

Lantern Android release packages are built in CI. You can build installers for beta, for production, or for internal testing by varying the tag syntax. To build for production, you simply tag the current version on `main` with, for example:
Lantern-client release and beta packages are built using Continuous Integration (CI). You can create installers for beta, production, or internal testing by adjusting the tag syntax.

#### Production Release for All Platforms 🌍

To release the production version for all platforms (including Android, iOS, and macOS), use the following command:

`git tag -a "lantern-7.0.0" -f -m "Tagging production release"`

Expand All @@ -241,9 +245,26 @@ Finally, to create an internal build, use "internal", as in:

`git tag -a "lantern-7.0.0-internal" -f -m "Tagging internal release"`

For all of the above, don't forget to push the tags:

`git push --tags -f`
#### Platform-Specific Releases 📱💻

For releasing to specific platforms, use the appropriate prefix:

* iOS: ios-
* Android: android-
* Desktop (Windows, macOS, Linux): desktop-

Example command for releasing a beta version for Android:

`git tag -a "android-lantern-7.0.0" -f -m "Tagging production release"`

This command will build and release the beta version for Android.

#### Pushing Tags to GitHub 🛠️

After creating a tag, push it to GitHub to trigger the CI/CD pipeline:

`git push origin [TAG-NAME]`or `git push origin lantern-7.0.0`

You can then find all built binaries in the [lantern-binaries repository](https://github.com/getlantern/lantern-binaries).

Expand Down

0 comments on commit 6c1eb44

Please sign in to comment.