:electron: Add reviewers to Flathub release pr & documentation (#6361)

* add reviewers to flathub pr

* release notes

* some docs for flathub release

* Update VRT screenshots

Auto-generated by VRT workflow

PR: #6361

* documentation

---------

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

.github/workflows/electron-master.yml

@@ -199,3 +199,4 @@ jobs:
             This PR updates the Actual desktop flatpak to version ${{ needs.build.outputs.version }}.
 
             :link: [View release notes](https://actualbudget.org/blog/release-${{ needs.build.outputs.version }})
+          reviewers: "jfdoming,MatissJanis,youngcw" # The core team that have accepted the collaborator access to the Flathub repo

packages/docs/docs/contributing/releasing.md

@@ -2,11 +2,9 @@
 
 In the open-source version of Actual, there are 3 NPM packages:
 
-[@actual-app/api](https://www.npmjs.com/package/@actual-app/api): The API for the underlying functionality. This includes the entire backend of Actual, meant to be used with Node.
-
-[@actual-app/web](https://www.npmjs.com/package/@actual-app/web): A web build that will serve the app with a web frontend. This includes both the frontend and backend of Actual. It includes the backend as well because it's built to be used as a Web Worker.
-
-[@actual-app/sync-server](https://www.npmjs.com/package/@actual-app/sync-server): The entire sync-server and underlying web client in one package. This includes a CLI tool, meant to be used with Node.
+- [@actual-app/api](https://www.npmjs.com/package/@actual-app/api): The API for the underlying functionality. This includes the entire backend of Actual, meant to be used with Node.
+- [@actual-app/web](https://www.npmjs.com/package/@actual-app/web): A web build that will serve the app with a web frontend. This includes both the frontend and backend of Actual. It includes the backend as well because it's built to be used as a Web Worker.
+- [@actual-app/sync-server](https://www.npmjs.com/package/@actual-app/sync-server): The entire sync-server and underlying web client in one package. This includes a CLI tool, meant to be used with Node.
 
 All packages and the main Actual release are versioned together. That makes it clear which version of the package should be used with the version of Actual.
 
@@ -40,7 +38,7 @@ For example:
 
 ## Trigger the release pipeline
 
-Once the release PRs have been merged, the commit in `actual` needs to be tagged. When the tag is pushed, it will trigger the Docker stable image, all NPM packages, and the Windows Store app to be built and published.
+Once the release PRs have been merged, the commit in `actual` needs to be tagged. When the tag is pushed, it will trigger the Docker stable image, all NPM package and the Desktop app to be built and published.
 
 - [ ] Run the below in the `actual` repository, or use the GitHub UI.
     ```bash
@@ -53,12 +51,15 @@ All NPM packages should be automatically released and pushed to the NPM registry
 - [@actual-app/web](https://www.npmjs.com/package/@actual-app/web)
 - [@actual-app/sync-server](https://www.npmjs.com/package/@actual-app/sync-server)
 
-A Windows Store update should be automatically generated 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 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 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 created, a Flatpak Build will be kicked off and will validated 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).
 
 ## Finalize the release
 
+- [ ] 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.
 - [ ] Wrap up by sending an announcement on Discord and Twitter.

upcoming-release-notes/6361.md

@@ -0,0 +1,7 @@
+---
+category: Maintenance
+authors: [MikesGlitch]
+---
+
+Automatically add core team as reviewers to the Flathub Release PR
+