github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-22 00:13:45 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

:electron: Flathub pr on publish of release assets (#7117)

Browse Source 
* flathub pr on publish of release

* docs

* release notes

* rabbit feedback
This commit is contained in:
Michael Clark
2026-03-04 17:05:47 +00:00
committed by GitHub
parent 3201819df9
commit 9e2793d413
4 changed files with 135 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
packages/docs/docs/contributing/releasing.md
View File

@@ -53,15 +53,15 @@ All NPM packages should be automatically released and pushed to the NPM registry
For the Windows Store desktop app, a submission will be automatically uploaded and submitted for certification. The certification process can take up to 3 business days; once complete the app will be in the Store. You can check the update status [here](https://partner.microsoft.com/en-us/dashboard) if you have permission. Note that the Store UI will not correctly reflect the submission status for about 30 minutes after submission.
For the Flathub desktop app, a draft PR will be created against the [Actual Flathub Repository](https://github.com/flathub/com.actualbudget.actual/pulls) and the core maintainers will be assigned as reviewers. Once published, a Flatpak Build will be kicked off and will validate the release. Once successful, the Core team will review the PR and merge it to `master`, which will kick off a production release to the Flathub Store. It can take anywhere from hours to a few days before the app will be available in the Flathub Store.
Finally, a draft GitHub release should be automatically created [here](https://github.com/actualbudget/actual/releases).
Once the GitHub release is published, the Flathub publish workflow will trigger for the Linux desktop app. A PR will be created against the [Actual Flathub Repository](https://github.com/flathub/com.actualbudget.actual/pulls) and the core maintainers will be assigned as reviewers. The Core team will review the PR and merge it to `master`, which will kick off a production release to the Flathub Store. It can take anywhere from hours to a few days before the app will be available in the Flathub Store.
## Finalize the release
- [ ] Publish, approve and merge the [Flathub Release PR](https://github.com/flathub/com.actualbudget.actual/pulls) to master.
- [ ] After the Docker image for the release is ready and pushed to Docker Hub, remember to deploy it and do a quick smoke test to verify things still work as expected.
- [ ] Un-draft the GitHub release which will send announcement notifications to all apps.
- [ ] Approve and merge the [Flathub Release PR](https://github.com/flathub/com.actualbudget.actual/pulls) to master.
- [ ] Wrap up by sending an announcement on Discord and Twitter.
- [ ] Wait one to two days to see if any new bugs show up that need a patch release. If none show up, end the merge freeze.