mirror of https://github.com/outbackdingo/firezone.git synced 2026-01-27 10:18:54 +00:00

Files

Jamil 1ec3db387e refactor: use script/bump-version.sh instead of Makefile (#7907 )

There isn't a good reason why we're using a Makefile instead of regular
Bash script for bumping versions, so this PR fixes that for better
maintainability.

It also reduces then chances for merge conflicts when bumping version
because the versions are longer on adjacent lines.

Fixes: #7904

2025-01-28 23:47:05 +00:00

3.3 KiB

Raw Blame History

Maintainer's Guide

This document contains instructions for maintaining the code in this repo including the product, website, and documentation.

Table of Contents:

Releasing
Apple Client
Breaking API Changes

Releasing

Note: The version for all published components is set from scripts/bump-versions.sh.

App Store clients (Apple/Android)

Go to Actions tab in GH and run the Kotlin or Swift workflow appropriately
This will push new release builds to Firebase or App Store Connect and pushed out Firebase App Distribution or TestFlight respectively.
Test this build manually a bit since we have no automated client tests yet
To submit for review:
- For Apple, do this through AppStore connect. Details are below.
- Android, download the AAB from Firebase App Distribution, create a new release in Google Play Console, and upload the AAB.

GitHub-released components (Linux, Windows, and Gateway)

Given that main is tested:

Go to the draft release of the component you want to publish
Double-check that the assets attached are from a recent CI and include the correct changes.
Publish the release. Tags and release name should be auto generated. This will trigger pushing Docker images to ghcr.io.
Open a PR and make the following changes:
Update scripts/bump-versions.sh with the new version number(s). Run scripts/bump-versions.sh to propagate the versions all components.
Update the Changelog (e.g. ../website/src/components/Changelog/GUI.tsx) with:
1. New version numbers
2. Release notes
3. Release date
4. Empty draft entry
Update the known issues in website/src/app/kb/client-apps/*
When the PR merges, the website will now redirect to the new version(s).

This results in a gap where GitHub knows about the release but nobody else does. This is okay because we can undo the GitHub release, and it prevents any queued PRs from landing in the release while you execute this process.

Apple Client

Log in to the following URL: https://appstoreconnect.apple.com/
Go to Apps
Go to Firezone
Click on TestFlight
- Note: You can't delete a Version in TestFlight
There is "internal testing" and "external testing"
- "internal testing" is only the Firezone team
- "external testing" is the beta customers
Click on the testing group you want to release to and on the testing group page:
- Click the + on the Builds sections
- Select the build you want to push out
- Check the Automatically notify testers
- Type a description of what you want users to see in the notification sent to users (e.g. a small change log of what's in this release)
- Click Submit for Review
  - Then you have to wait for it to be reviewed (has been a matter of minutes as of late)

(Alternative way to push out a release)

After login go to Builds (select either ios/macos)
Find the Version section you want to release and drop down to show list of builds
Find the build you want to push out, hover over the Groups column and select the + icon
From here it's the same as the instructions above to type a description, etc...

Breaking API changes

We should notify customers 2 weeks in advance for any API-breaking changes.

3.3 KiB Raw Blame History