session-desktop/RELEASING.md

# Releasing

Creating a new Session Desktop release is very simple.

1.  Bump up the version in `package.json`.
2.  Merge all changes required into the `master` branch.
    - This will trigger github actions to start building a draft release
3.  After github actions has finished building. Go to Release page in the repository.
4.  Click on the draft release and change the tag target to `master`.
5.  Add in release notes.
6.  Generate gpg signatures.
7.  Click publish release.

## Notes

Artifacts attached in the release shouldn't be deleted! These include the yml files (latest, latest-mac, latest-linux). These are all necessary to get auto updating to work correctly.

### Mac

Mac currently uses 2 formats `dmg` and `zip`.
We need the `zip` format for auto updating to work correctly.
We also need the `dmg` because on MacOS Catalina, there is a system bug where extracting the artifact `zip` using the default _Archive Utility_ will make it so the extracted application is invalid and it will fail to open. A work around for this is to extract the `zip` using an alternate program such as _The Unarchiver_.

Once this bug is fixed we can go back to using the `zip` format by itself.

## Linux Flatpak

Flatpak generation is different from the normal build process and is not directly managed by the Session Technology Foundation. When a new version of Session Desktop is released, a Flathub operated bot will make a Pull Request on the [Session Flathub Repo](https://github.com/flathub/network.loki.Session) to repackage the release into a Flatpak and release it on Flathub.
Fix auto updating on all platforms. Added instructions for release. 5 years ago			`# Releasing`

			`Creating a new Session Desktop release is very simple.`

			1. Bump up the version in `package.json`.
			2. Merge all changes required into the `master` branch.
feat: update internal builds and release documentation 3 months ago			`- This will trigger github actions to start building a draft release`
Fix auto updating on all platforms. Added instructions for release. 5 years ago			`3. After github actions has finished building. Go to Release page in the repository.`
			4. Click on the draft release and change the tag target to `master`.
			`5. Add in release notes.`
			`6. Generate gpg signatures.`
			`7. Click publish release.`

			`## Notes`

			`Artifacts attached in the release shouldn't be deleted! These include the yml files (latest, latest-mac, latest-linux). These are all necessary to get auto updating to work correctly.`

			`### Mac`

			Mac currently uses 2 formats `dmg` and `zip`.
			We need the `zip` format for auto updating to work correctly.
			We also need the `dmg` because on MacOS Catalina, there is a system bug where extracting the artifact `zip` using the default _Archive Utility_ will make it so the extracted application is invalid and it will fail to open. A work around for this is to extract the `zip` using an alternate program such as _The Unarchiver_.

			Once this bug is fixed we can go back to using the `zip` format by itself.
Update RELEASING.md 5 years ago
			`## Linux Flatpak`

chore: update flatpak release info 3 months ago			`Flatpak generation is different from the normal build process and is not directly managed by the Session Technology Foundation. When a new version of Session Desktop is released, a Flathub operated bot will make a Pull Request on the [Session Flathub Repo](https://github.com/flathub/network.loki.Session) to repackage the release into a Flatpak and release it on Flathub.`