Skip to content

Commit 5387c73

Browse files
committed
docs: add Flathub manifest update step to release process
Add documentation for updating the Flathub manifest (flathub/org.dash.dash-core) as part of the post-release checklist. This includes updating download URLs, SHA256 hashes, and the metainfo.xml source reference for each new release. Requested-by: knst in #7183
1 parent af926ae commit 5387c73

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

doc/release-process.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -239,6 +239,12 @@ popd
239239
* [ ] Submit patches to BTCPay to ensure they use latest / compatible version see https://github.com/dashpay/dash/issues/4211#issuecomment-966608207
240240
* [ ] Update Core and User docs (docs.dash.org)
241241
* [ ] Test Docker build runs without error in Dashmate
242+
* [ ] Update the [Flathub manifest](https://github.com/flathub/org.dash.dash-core) with the new release:
243+
- Update the download URLs in `org.dash.dash-core.json` to point to the new release tag
244+
- Update the SHA256 hashes for the `x86_64` and `aarch64` Linux tarballs
245+
- Update the `metainfo.xml` source URL to reference the new release tag commit
246+
- Open a PR against `flathub/org.dash.dash-core` and verify the Flathub build succeeds
247+
- See [previous update PR](https://github.com/flathub/org.dash.dash-core/commit/7f5f9dd8a464ec5e2cf2d657205261c19ac1a5a8) for an example
242248
* [ ] Add new Release Process items to repo [Release Process](release-process.md) document
243249
* [ ] Merge `master` branch back into `develop` so that `master` could be fast-forwarded on next release again
244250

0 commit comments

Comments
 (0)