diff --git a/.github/workflows/electron-master.yml b/.github/workflows/electron-master.yml
index 0dc428c76a..e54529e2bc 100644
--- a/.github/workflows/electron-master.yml
+++ b/.github/workflows/electron-master.yml
@@ -199,6 +199,7 @@ jobs:
           token: ${{ secrets.FLATHUB_GITHUB_TOKEN }}
           commit-message: 'Update Actual flatpak to version ${{ needs.build.outputs.version }}'
           branch: 'release/${{ needs.build.outputs.version }}'
+          draft: true
           title: 'Update Actual flatpak to version ${{ needs.build.outputs.version }}'
           body: |
             This PR updates the Actual desktop flatpak to version ${{ needs.build.outputs.version }}.
diff --git a/packages/docs/docs/contributing/releasing.md b/packages/docs/docs/contributing/releasing.md
index 67e537f1e0..2dd7ad69ca 100644
--- a/packages/docs/docs/contributing/releasing.md
+++ b/packages/docs/docs/contributing/releasing.md
@@ -53,13 +53,13 @@ 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 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.
+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).
 
 ## Finalize the release
 
-- [ ] Approve and merge the [Flathub Release PR](https://github.com/flathub/com.actualbudget.actual/pulls) to master.
+- [ ] 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.
 - [ ] Wrap up by sending an announcement on Discord and Twitter.
diff --git a/upcoming-release-notes/6910.md b/upcoming-release-notes/6910.md
new file mode 100644
index 0000000000..7860aea074
--- /dev/null
+++ b/upcoming-release-notes/6910.md
@@ -0,0 +1,6 @@
+---
+category: Maintenance
+authors: [MikesGlitch]
+---
+
+Automated the Flathub release PR to be draft until we publish the main release.