docs: add Flathub manifest update steps to release process

[thepastaclaw]

Summary

Adds a Flathub manifest update checklist to the release process documentation, as requested by knst in #7183.

The new checklist covers updating the Flathub manifest (org.dash.dash-core.json) with download URLs, SHA256 hashes, and metainfo.xml source references for each new release, plus submitting a PR to flathub/org.dash.dash-core.

Validation

• Markdown lint clean
• Inserted in the correct location within the "After the release" section
• Links to an example commit for reference

[thepastaclaw]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[github-actions]

✅ No Merge Conflicts Detected

This PR currently has no conflicts with other open PRs.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 69ced6c5-4e33-4eb0-ad5e-0b0d89acbdf5

📥 Commits

Reviewing files that changed from the base of the PR and between af926ae and 5387c73.

📒 Files selected for processing (1)

• doc/release-process.md

---

Walkthrough

This pull request updates the release process documentation by adding a new checklist item under the "After the release" section. The addition provides steps for updating the Flathub manifest following a release, including instructions to update download URLs, SHA256 hashes for x86_64 and aarch64 tarballs, metainfo source URL, and guidance for opening a pull request against Flathub with reference to a prior example.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding Flathub manifest update steps to the release process documentation.
Description check	✅ Passed	The description is clearly related to the changeset, providing context about the Flathub manifest update checklist and validation performed.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[knst]

Update flatpak metainfo file with latest release tag and estimated release date

Sorry, I am blind, it's already here in the release-process.md, my comment at #7183 (comment) is irrelevant